What does polygon-automation do?

Automates Polygon operations through Rube MCP and Composio's Polygon toolkit, using live tool schemas discovered with RUBE_SEARCH_TOOLS.

What commands are used?

Key commands include RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, RUBE_MULTI_EXECUTE_TOOL, and optionally RUBE_REMOTE_WORKBENCH or RUBE_GET_TOOL_SCHEMAS.

What prerequisites must be in place?

Rube MCP connection, an active Polygon connection via the polygon toolkit, and RUBE_SEARCH_TOOLS ready to return tool schemas.

polygon-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Polygon Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/polygon

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Polygon operations through Composio's Polygon toolkit via Rube MCP. This skill orchestrates discovery, connection, and execution using live tool schemas. Always fetch current tool schemas before running workflows to stay aligned with updates.

How This Skill Works

You discover available tools with RUBE_SEARCH_TOOLS for your use case. Then verify ACTIVE connection with RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool with RUBE_MULTI_EXECUTE_TOOL, including memory and session_id.

When to Use It

You need to perform a specific Polygon operation after discovering tools via RUBE_SEARCH_TOOLS.
You must verify that the Polygon connection is ACTIVE before executing tools.
You want to reuse a session ID across steps within a workflow.
You need to perform bulk Polygon operations using RUBE_REMOTE_WORKBENCH.
You want to fetch full tool schemas and references using RUBE_GET_TOOL_SCHEMAS.

Quick Start

Step 1: Verify RUBE MCP is connected and RUBE_SEARCH_TOOLS responds.
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkit 'polygon' and ensure the status is ACTIVE.
Step 3: Use RUBE_SEARCH_TOOLS to discover tools, then execute a tool with RUBE_MULTI_EXECUTE_TOOL including memory and session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get current tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools.
Use exact field names and types from the search results (no hardcoding).
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new IDs for new workflows.

Example Use Cases

Discover available Polygon tools with RUBE_SEARCH_TOOLS for a desired use_case, then select a tool slug and execute it via RUBE_MULTI_EXECUTE_TOOL.
Establish and validate an ACTIVE Polygon connection using RUBE_MANAGE_CONNECTIONS before running any workflow.
Run a sequence of tools in a single session by reusing a session_id across RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL.
Perform bulk Polygon operations using RUBE_REMOTE_WORKBENCH and a prepared tool slug with proper memory payload.
Retrieve full tool schemas with RUBE_GET_TOOL_SCHEMAS to audit or document available inputs.

Frequently Asked Questions

Add this skill to your agents