How do I ensure tool schemas are current?

Always run RUBE_SEARCH_TOOLS before execution to fetch the latest tool slugs and input schemas.

Do I need to include a memory object in every tool call?

Yes. Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if it's an empty object.

When can I start executing tools?

Only after RUBE_MANAGE_CONNECTIONS reports ACTIVE and RUBE_SEARCH_TOOLS has returned usable tool slugs and schemas.

moco-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Moco Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/moco

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Moco operations through Composio's toolkit using Rube MCP. The workflow emphasizes always discovering current tool schemas before execution and covers setup, connection management, and running tools in a structured sequence.

How This Skill Works

Connect Rube MCP to the Moco toolkit, verify readiness with RUBE_SEARCH_TOOLS, and then discover available tools. Ensure the connection is ACTIVE via RUBE_MANAGE_CONNECTIONS before executing tools with RUBE_MULTI_EXECUTE_TOOL, including a memory object and session_id to maintain state across steps.

When to Use It

Automating recurring Moco operations that require up-to-date tool schemas
When tool slugs or input fields may change between runs
To verify an ACTIVE Moco connection before performing workflows
When executing a sequence of tools in a single session
When handling paginated or updated tool schema responses

Quick Start

Step 1: Add the MCP server (https://rube.app/mcp) and verify RUBE_SEARCH_TOOLS responds
Step 2: Discover available Moco tools with RUBE_SEARCH_TOOLS for your use case
Step 3: Check ACTIVE connection with RUBE_MANAGE_CONNECTIONS and run tools via RUBE_MULTI_EXECUTE_TOOL, including memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current schemas
Check RUBE_MANAGE_CONNECTIONS status and ensure it is ACTIVE before running tools
Use exact field names and types from the search results; avoid hardcoding slugs
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty ({})
Reuse session IDs within a workflow and generate new ones for new workflows

Example Use Cases

Schedule a nightly Moco data export by discovering the appropriate tool via RUBE_SEARCH_TOOLS and executing it with a persistent session
Run a batch of Moco maintenance tasks (cleanup, reindex) by discovering tools and executing them in sequence within a single session
Perform a health-check workflow that verifies tool availability and confirms an ACTIVE Moco connection
Execute multiple Moco tools in one run using RUBE_MULTI_EXECUTE_TOOL to complete a composite operation
Fetch updated tool schemas with RUBE_GET_TOOL_SCHEMAS after discovery to handle pagination or schema changes

Frequently Asked Questions

Add this skill to your agents