How do I start Paradym automation with Rube MCP?

Add the Rube MCP endpoint, verify RUBE_SEARCH_TOOLS, manage the Paradym connection, then discover and execute tools using RUBE_MULTI_EXECUTE_TOOL.

Why must I search tools first?

Tool schemas change over time; RUBE_SEARCH_TOOLS returns current tool slugs and input schemas, preventing hardcoded errors.

What if the Paradym connection is not ACTIVE?

Follow the auth link returned by RUBE_MANAGE_CONNECTIONS to complete setup, then re-check status until ACTIVE before running workflows.

paradym-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Paradym Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/paradym

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Paradym operations through Composio's Paradym toolkit via Rube MCP. It relies on RUBE_SEARCH_TOOLS to fetch current tool schemas and uses RUBE_MULTI_EXECUTE_TOOL to run chosen tools, ensuring ACTIVE connectivity.

How This Skill Works

1) Discover available Paradym tools with RUBE_SEARCH_TOOLS. 2) Verify the Paradym connection is ACTIVE with RUBE_MANAGE_CONNECTIONS. 3) Execute the selected tool via RUBE_MULTI_EXECUTE_TOOL, including a memory object and the session_id.

When to Use It

Starting a Paradym workflow and you need up-to-date tool schemas from RUBE_SEARCH_TOOLS
Ensuring the Paradym connection is ACTIVE before running any tools
Exploring which Paradym tools are available for a specific use case
Executing a discovered Paradym tool with proper arguments and session management
Handling large result sets or multiple tools by using pagination and repeated discovery

Quick Start

Step 1: Add the Rube MCP endpoint (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS responds
Step 2: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["paradym"] and complete auth if required
Step 3: Discover tools for your Paradym task with RUBE_SEARCH_TOOLS, then execute a tool via RUBE_MULTI_EXECUTE_TOOL using a session_id and memory object

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch up-to-date tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools
Use exact field names and types from the search results to ensure schema compliance
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
Reuse session IDs within a workflow and generate new IDs for new workflows; watch for pagination

Example Use Cases

Automate a Paradym data export by discovering tools with RUBE_SEARCH_TOOLS and executing the chosen tool with prepared arguments
Maintain a long-running Paradym workflow by reusing a session_id across steps and confirming ACTIVE status
Integrate RUBE_MANAGE_CONNECTIONS to ensure the Paradym toolkit is ACTIVE before executing a tool
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to reference schemaRef before running
Paginate through tool lists and fetch all available Paradym tools using RUBE_SEARCH_TOOLS and pagination tokens

Frequently Asked Questions

Add this skill to your agents