Do I need API keys to use Polygon IO automation?

No API keys are needed — add the MCP endpoint and ensure an active Rube MCP connection with the polygon_io toolkit.

What if tool slugs change?

Always call RUBE_SEARCH_TOOLS to fetch current schemas; do not hardcode tool slugs or arguments.

Is memory required in every tool execution?

Yes — memory must be included in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({})

polygon-io-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Polygon IO Automation via Rube MCP

Automate Polygon IO operations through Composio's Polygon IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/polygon_io

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active Polygon IO connection via RUBE_MANAGE_CONNECTIONS with toolkit polygon_io
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 polygon_io
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: "Polygon IO 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 Polygon IO task"}]
session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["polygon_io"]
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 Polygon IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `polygon_io`
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/polygon-io-automation/SKILL.mdView on GitHub

Overview

Automate Polygon IO operations using Composio's Rube MCP toolkit. This workflow relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and requires an active Polygon IO connection, ensuring tool definitions stay up to date without hardcoding slugs.

How This Skill Works

It discovers available tools with RUBE_SEARCH_TOOLS for your Polygon IO use case and reads their input schemas. It then checks or establishes an ACTIVE connection via RUBE_MANAGE_CONNECTIONS for the polygon_io toolkit. Finally, it runs the selected tool with RUBE_MULTI_EXECUTE_TOOL, including memory and the exact arguments from the schema.

When to Use It

Starting a new Polygon IO workflow where you want the latest tool schemas
Verifying or establishing an ACTIVE Polygon IO connection before operations
Discovering tool slugs and input fields for a specific Polygon IO task
Executing a discovered tool with the correct arguments for a Polygon IO operation
Running bulk or multi-tool Polygon IO tasks in a single session

Quick Start

Step 1: Verify Rube MCP is available by running RUBE_SEARCH_TOOLS
Step 2: Connect to Polygon IO with RUBE_MANAGE_CONNECTIONS and ensure status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS for your use case, then run a tool with RUBE_MULTI_EXECUTE_TOOL using the provided memory payload

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the discovered input schemas; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination when responses are paginated

Example Use Cases

Automate daily Polygon IO balance retrieval by discovering the appropriate tool and executing it
Fetch historical price data for a symbol using a discovered Polygon IO tool slug
Synchronize Polygon IO trades data to a data warehouse in a batch run
Validate connection to Polygon IO and run a trades-related tool in a test session
Execute a multi-step Polygon IO workflow across multiple tool executions in a single session

Frequently Asked Questions

Add this skill to your agents