Rube MCP is Composio's middleware that lets you discover, manage, and execute Optimoroute tools programmatically.

Do I need API keys to use this skill?

No API keys are required. You connect to the MCP endpoint (e.g., https://rube.app/mcp) and authorize via the provided flow.

What if tool schemas change?

Always call RUBE_SEARCH_TOOLS to refresh schemas before execution; rely on the latest field names and types from the search results and include memory in calls.

optimoroute-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Optimoroute Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/optimoroute

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

Automate Optimoroute operations via Composio's Rube MCP toolkit. Always fetch current tool schemas before running workflows to avoid drift and errors.

How This Skill Works

Connect and verify Rube MCP availability using RUBE_SEARCH_TOOLS. Discover available Optimoroute tools, then check the connection with RUBE_MANAGE_CONNECTIONS and set it to ACTIVE before executing. Use RUBE_MULTI_EXECUTE_TOOL to run a chosen tool with the required arguments and a memory payload; reuse session IDs to chain steps in a single workflow.

When to Use It

Automating routine Optimoroute tasks (e.g., daily route optimization) using scripted tool runs
When tool schemas may change and you must fetch them first to ensure correct inputs
To establish and validate a live connection to Optimoroute before executing tools
For executing multiple tools in a single workflow within one session
When performing bulk or remote orchestrations using RUBE_MULTI_EXECUTE_TOOL

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm availability
Step 3: Discover tools with RUBE_SEARCH_TOOLS, pick a tool_slug, and run RUBE_MULTI_EXECUTE_TOOL with memory: {} and your session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to get the latest tool schemas
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE status before running tools
Use exact field names and types from the tool discovery results, not hardcoded values
Include memory: {} in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and paginate tool discovery if results are paginated

Example Use Cases

Nightly route optimization: discover available Optimoroute tools, validate the ACTIVE connection, and execute the top-level optimization tool using the latest schema
Multi-step planning in one session: chain route planning followed by load balancing by executing discovered tool slugs with memory state between calls
Schema drift handling: when a new tool schema is published, refresh tools with RUBE_SEARCH_TOOLS before executing
Connection health check: schedule a daily health check that ensures RUBE_MANAGE_CONNECTIONS reports ACTIVE before tool execution
Paginated tool discovery: fetch tool pages until complete, then select a tool_slug and execute via RUBE_MULTI_EXECUTE_TOOL

Frequently Asked Questions

Add this skill to your agents