Token Metrics Automation

What This Skill Does

This skill automates Token Metrics operations using Composio's toolkit through Rube MCP. It allows users to programmatically access and manage token-related data and workflows. It is designed for developers and analysts working with token metrics data.

When to Use

• Automate fetching of token prices.
• Analyze token holder distribution.
• Monitor token transaction volumes.
• Generate reports on token performance.
• Track token supply changes.
• Integrate token data into dashboards.

Key Features

Discovers available tools via RUBE_SEARCH_TOOLS. Manages connections using RUBE_MANAGE_CONNECTIONS. Executes tools with RUBE_MULTI_EXECUTE_TOOL. Provides access to Composio's Token Metrics toolkit. Requires active connection to the Token Metrics toolkit. Emphasizes schema compliance for tool arguments.

Manual Installation

Manual installation View Full Skill Content The complete markdown content that gets installed Token Metrics Automation via Rube MCP

Automate Token Metrics operations through Composio's Token Metrics toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/token_metrics

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["token_metrics"] 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

Automate Token Metrics operations through Composio's Token Metrics toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/token_metrics