What is Rube MCP and how does opencage-automation use it?

Rube MCP is Composio's management plane. This skill uses it to discover opencage tool schemas, manage connections, and execute tools.

Why must I call RUBE_SEARCH_TOOLS first?

Tool schemas can change; querying first ensures you use current tool slugs and correct argument schemas.

What if the connection is not ACTIVE?

Follow the returned auth link to complete setup, then re-check with RUBE_MANAGE_CONNECTIONS until ACTIVE before running tools.

opencage-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Opencage Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/opencage

Prerequisites

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

Step 2: Check Connection

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

Overview

This skill automates Opencage operations through Composio's Opencage toolkit using Rube MCP. It emphasizes always calling RUBE_SEARCH_TOOLS first to fetch current schemas and avoid hardcoding tool slugs.

How This Skill Works

Connect Rube MCP and verify RUBE_SEARCH_TOOLS returns tool slugs and schemas. Then activate the opencage toolkit with RUBE_MANAGE_CONNECTIONS and execute tools with RUBE_MULTI_EXECUTE_TOOL, supplying exact arguments and a memory object. Always reuse a session_id for related steps.

When to Use It

Integrating an Opencage task into an automated workflow in Composio.
When tool schemas may change and you must fetch them with RUBE_SEARCH_TOOLS before running.
When you need to verify that the Opencage connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before execution.
When executing a sequence of Opencage tools within a single session using RUBE_MULTI_EXECUTE_TOOL.
When performing bulk or chained Opencage actions and ensuring up-to-date tool schemas.

Quick Start

Step 1: Add Rube MCP as an MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds.
Step 2: Discover tools with RUBE_SEARCH_TOOLS using the Opencage use_case and start a session.
Step 3: Connect the toolkit with RUBE_MANAGE_CONNECTIONS (toolkit: opencage), then run tools with RUBE_MULTI_EXECUTE_TOOL inside the session.

Best Practices

Always start with RUBE_SEARCH_TOOLS to obtain up-to-date tool slugs and schemas.
Check that RUBE_MANAGE_CONNECTIONS shows an ACTIVE status before executing tools.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({}).
Reuse session IDs within a workflow and generate new IDs for new workflows.
Handle pagination tokens when discovering tools and fetch complete results.

Example Use Cases

Geocode a batch of addresses by discovering the 'geocode' tool slug and running it with a prepared argument set.
Reverse geocode coordinates after establishing an ACTIVE opencage connection.
Run a sequence of Opencage operations in a single session, reusing session_id across steps.
Discover tools with RUBE_SEARCH_TOOLS, handle pagination, then execute multiple tools via RUBE_MULTI_EXECUTE_TOOL.
Bulk Opencage operations using RUBE_REMOTE_WORKBENCH run_composio_tool() for scalable processing.

Frequently Asked Questions

Add this skill to your agents