What is benzinga-automation?

A Composio skill to automate Benzinga tasks via Rube MCP, with live tool schemas checked first.

What do I need to start?

Rube MCP connected at https://rube.app/mcp, an active Benzinga connection via the benzinga toolkit, and the habit to call RUBE_SEARCH_TOOLS first.

Why must I search for tools first?

Tool schemas change; hardcoding slugs and args can break workflows. Searching ensures you have current slugs, input schemas, and execution plans.

benzinga-automation

Scanned

npx machina-cli add skill ComposioHQ/awesome-claude-skills/benzinga-automation --openclaw

Files (1)

SKILL.md

2.9 KB

Benzinga Automation via Rube MCP

Automate Benzinga operations through Composio's Benzinga toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/benzinga

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Benzinga connection via RUBE_MANAGE_CONNECTIONS with toolkit benzinga
Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit benzinga
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS
queries: [{use_case: "Benzinga operations", known_fields: ""}]
session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS
queries: [{use_case: "your specific Benzinga task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["benzinga"]
session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL
tools: [{
  tool_slug: "TOOL_SLUG_FROM_SEARCH",
  arguments: {/* schema-compliant args from search results */}
}]
memory: {}
session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
Schema compliance: Use exact field names and types from the search results
Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})
Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows
Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference

Operation	Approach
Find tools	`RUBE_SEARCH_TOOLS` with Benzinga-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `benzinga`
Execute	`RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs
Bulk ops	`RUBE_REMOTE_WORKBENCH` with `run_composio_tool()`
Full schema	`RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef`

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/benzinga-automation/SKILL.mdView on GitHub

Overview

Automate Benzinga operations through Composio's Benzinga toolkit via Rube MCP. Always search for current tool schemas before running workflows to ensure slugs and arguments are up to date, and verify an ACTIVE Benzinga connection.

How This Skill Works

Use RUBE_SEARCH_TOOLS to discover available Benzinga tools and their input schemas. Then connect via RUBE_MANAGE_CONNECTIONS with the benzinga toolkit and perform RUBE_MULTI_EXECUTE_TOOL calls using discovered tool_slugs and required arguments, including memory, within a session. Always check the connection is ACTIVE and reuse session IDs where possible.

When to Use It

You're automating a Benzinga operation and need up-to-date tool schemas
You want to build a multi-step Benzinga workflow that uses several tools in sequence
You must verify the Benzinga connection is ACTIVE before executing tools
You are handling paginated results and need to fetch all pages
You want to avoid hardcoding tool slugs by fetching them dynamically with RUBE_SEARCH_TOOLS

Quick Start

Step 1: Get Rube MCP: add https://rube.app/mcp as an MCP server in your client config
Step 2: Verify availability: run RUBE_SEARCH_TOOLS to confirm responses
Step 3: Connect and execute: use RUBE_MANAGE_CONNECTIONS for benzinga, then RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug and memory: {} and your session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the search results
Always include memory in RUBE_MULTI_EXECUTE_TOOL calls
Reuse session IDs within a workflow and avoid unnecessary new sessions

Example Use Cases

Discover Benzinga tools for a use case like earnings news and execute the matching tool slug with required arguments
Create a 3-step workflow to fetch latest Benzinga headlines for a watchlist and summarize them
Run a sequence of tools to monitor a stock and alert on news while reusing a session
Adapt to updated tool schemas by re-running RUBE_SEARCH_TOOLS before changes
Handle pagination in responses to fetch all pages of data from a Benzinga tool

Frequently Asked Questions

Add this skill to your agents