Polygon Automation

What This Skill Does

This skill automates Polygon operations using Composio's Polygon toolkit through Rube MCP. It's designed for users who need to streamline their interactions with the Polygon blockchain. The skill ensures proper setup and tool discovery for efficient workflow execution.

When to Use

Discover available Polygon tools. Check the status of the Polygon connection. Execute specific Polygon tools. Automate blockchain interactions. Streamline Polygon workflows. Manage Polygon operations efficiently.

Key Features

Automates Polygon operations via Rube MCP. Uses Composio's Polygon toolkit. Requires an active Polygon connection. Employs RUBE_SEARCH_TOOLS for tool discovery. Checks connection status with RUBE_MANAGE_CONNECTIONS. Executes tools using RUBE_MULTI_EXECUTE_TOOL.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedPolygon 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

Powered by Composio