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

Always run RUBE_SEARCH_TOOLS before executing; it returns current tool slugs, input schemas, and recommended execution plans.

What if the Tomtom connection is not ACTIVE?

Use the auth link provided by RUBE_MANAGE_CONNECTIONS to complete setup, then verify ACTIVE before workflows.

Do I need to include memory in tool executions?

Yes. Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty, to preserve state and session context.

tomtom-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Tomtom Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/tomtom

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Tomtom operations through Composio's Tomtom toolkit using Rube MCP. It orchestrates discovery, connection verification, and tool execution by calling RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL, always using current tool schemas and an active connection.

How This Skill Works

The workflow begins by discovering available Tomtom tools with RUBE_SEARCH_TOOLS to obtain up-to-date slugs and input schemas. It then verifies and establishes an ACTIVE Tomtom connection via RUBE_MANAGE_CONNECTIONS. Finally, it executes the selected tool with RUBE_MULTI_EXECUTE_TOOL, supplying schema-compliant arguments, a memory object, and a session_id for continuity.

When to Use It

Automating recurring Tomtom operations end-to-end in a single workflow.
When tool schemas may change and you must fetch current slugs and arguments first.
To reuse a session across a multi-step Tomtom workflow while maintaining state.
Before executing tools to ensure the Tomtom connection is ACTIVE.
For bulk or chained Tomtom tasks using multi-tool execution or bulk ops.

Quick Start

Step 1: Add Rube MCP server at https://rube.app/mcp (no API keys needed).
Step 2: Verify RUBE_SEARCH_TOOLS responds, then call RUBE_MANAGE_CONNECTIONS with toolkits: ["tomtom"] and ensure ACTIVE.
Step 3: Discover tools, check the connection, and run a tool with RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to obtain current tool slugs and schemas.
Check RUBE_MANAGE_CONNECTIONS returns ACTIVE before running any tools.
Use exact field names and types from the discovered tool schemas.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}).
Reuse session IDs within a workflow; generate new ones for new workflows and watch for pagination.

Example Use Cases

Discover a Tomtom operation, establish a connection, and run the TOOL_SLUG_FROM_SEARCH with the required arguments and a session.
Chain multiple Tomtom tools in a single session using RUBE_MULTI_EXECUTE_TOOL and memory to maintain state.
Perform bulk Tomtom tasks via RUBE_REMOTE_WORKBENCH with run_composio_tool() for parallel execution.
Inspect available tool schemas with RUBE_GET_TOOL_SCHEMAS to understand input requirements.
Handle pagination in tool discovery responses, continuing fetches until all tools are retrieved.

Frequently Asked Questions

Add this skill to your agents