How do I ensure tool schemas stay current?

Always call RUBE_SEARCH_TOOLS before executing and avoid hardcoding tool slugs or arguments; rely on the returned schemas.

What if the Platerecognizer connection isn't ACTIVE?

Follow the auth link provided by the response to complete setup, then re-check that the status is ACTIVE before running workflows.

Do I need to include memory in tool calls?

Yes. Include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if it is empty, to satisfy the schema requirements.

platerecognizer-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Platerecognizer Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/platerecognizer

Prerequisites

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

Step 2: Check Connection

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

View on GitHub

Overview

This skill automates Platerecognizer operations through Composio's Rube MCP toolkit. It emphasizes discovering current tool schemas before execution to adapt to changes and avoid broken integrations.

How This Skill Works

Connect to Rube MCP and verify the Platerecognizer toolkit connection. Discover available tools with RUBE_SEARCH_TOOLS, then validate an ACTIVE connection with RUBE_MANAGE_CONNECTIONS. Execute tools using RUBE_MULTI_EXECUTE_TOOL with the discovered tool slug and a schema-compliant argument set, including memory, within a session.

When to Use It

When starting a Platerecognizer task and tool schemas may have changed, requiring fresh discovery
When integrating Platerecognizer into a larger Composio workflow and you must discover tools first
When you need to ensure the Platerecognizer connection is ACTIVE before running workflows
When coordinating multiple tool executions within a single session and reusing the session ID
When handling paginated tool results and ensuring memory is included in calls

Quick Start

Step 1: Configure MCP endpoint and verify availability with RUBE_SEARCH_TOOLS
Step 2: Manage the Platerecognizer connection via RUBE_MANAGE_CONNECTIONS and ensure ACTIVE
Step 3: Discover tools, then execute with RUBE_MULTI_EXECUTE_TOOL using memory and the session

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to obtain current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status prior to tool execution
Use exact field names and types from the tool schemas returned by search
Include a memory object in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and manage pagination tokens until complete

Example Use Cases

Automate a batch of license-plate recognitions where tool slugs/args update, using RUBE_SEARCH_TOOLS to adapt each run
Establish a Platerecognizer connection, discover tools, and run a recognition workflow in a single session
Chain multiple Platerecognizer tools discovered in the same session to process a batch of images
Use RUBE_REMOTE_WORKBENCH with run_composio_tool() for bulk operations on plates dataset
Query full tool schemas with RUBE_GET_TOOL_SCHEMAS to validate arguments before execution

Frequently Asked Questions

Add this skill to your agents