What is Rube MCP and why should I use it for Coinmarketcal?

Rube MCP is an MCP server that orchestrates Coinmarketcal tool access and execution; it ensures you always use current tool schemas and a standardized workflow.

Do I need API keys to use Coinmarketcal automation?

No API keys are required. You add the rube MCP endpoint (e.g., https://rube.app/mcp) as the MCP server in your client configuration.

How do I ensure tool schemas stay up-to-date?

Always run RUBE_SEARCH_TOOLS before executing any tool to pull the latest available slugs, schemas, and execution plans; avoid hardcoding slugs or argument fields.

coinmarketcal-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Coinmarketcal Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/coinmarketcal

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["coinmarketcal"]
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 Coinmarketcal-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `coinmarketcal`
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/coinmarketcal-automation/SKILL.md

View on GitHub

Overview

This skill automates Coinmarketcal workflows using Composio's Coinmarketcal toolkit via Rube MCP. It centralizes tool discovery, connection management, and execution, ensuring tool schemas are current and workflows run smoothly. It’s essential for teams that repeatedly manage Coinmarketcal operations without manual setup.

How This Skill Works

Connect to Rube MCP and confirm RUBE_SEARCH_TOOLS is available. Discover Coinmarketcal tools, then manage the Coinmarketcal connection with RUBE_MANAGE_CONNECTIONS. Finally, execute the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and the required arguments, always including memory and a session_id.

When to Use It

Setting up a new Coinmarketcal workflow and discovering available tools
Performing a prepared Coinmarketcal operation after confirming an ACTIVE connection
Refreshing tool schemas to adapt to updated tool definitions
Batching multiple Coinmarketcal actions in a single session
Troubleshooting by reusing an existing session_id and validating connection status

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Coinmarketcal operations' to discover tools
Step 2: RUBE_MANAGE_CONNECTIONS for toolkit 'coinmarketcal' and confirm ACTIVE
Step 3: RUBE_MULTI_EXECUTE_TOOL with the selected tool_slug and proper arguments, include memory and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools
Use exact field names and types from the tool schemas; avoid hardcoding slugs
Include memory in each RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session_ids within a workflow and generate new ones for new workflows

Example Use Cases

Discover available Coinmarketcal tools with a specific use_case, then select a tool slug for execution
Establish and verify an ACTIVE Coinmarketcal connection before running a workflow
Execute a discovered tool using the required arguments returned by RUBE_SEARCH_TOOLS
Resume a partially completed workflow by reusing the existing session_id
Perform bulk actions by using RUBE_REMOTE_WORKBENCH and run_composio_tool() with multiple tools

Frequently Asked Questions

Add this skill to your agents