Do I need an API key to use Parma automation?

No keys are required. Add the Rube MCP endpoint to your client configuration and manage authentication via RUBE_MANAGE_CONNECTIONS.

What should I do if tool schemas change?

Always call RUBE_SEARCH_TOOLS first and avoid hardcoding slugs or arguments; update your inputs based on the latest schemas.

How do I confirm readiness before running workflows?

Check that RUBE_SEARCH_TOOLS returns tool slugs for your Parma task and that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.

parma-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Parma Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/parma

Prerequisites

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

Step 2: Check Connection

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

Overview

Parma Automation via Rube MCP enables programmatic control of Parma tasks through Composio's Parma toolkit. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before running any workflows. The setup requires a connected Rube MCP and an active Parma connection.

How This Skill Works

Connect Rube MCP to Parma and use RUBE_SEARCH_TOOLS to fetch up-to-date tool slugs and input schemas. Then verify the Parma connection with RUBE_MANAGE_CONNECTIONS and, when ready, execute tools with RUBE_MULTI_EXECUTE_TOOL using the discovered slug and schema-compliant arguments.

When to Use It

Automate Parma operations at scale by leveraging discovered tools instead of hard-coded slugs.
Before executing any Parma workflow, fetch the current tool schemas to ensure compatibility.
Validate the Rube MCP connection is ACTIVE prior to tool execution.
Run multi-tool Parma workflows within a single session to improve efficiency.
Handle large results with pagination by iterating through RUBE_SEARCH_TOOLS responses.

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration.
Step 2: Run RUBE_SEARCH_TOOLS to discover available Parma tools and their input schemas.
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkits: ["parma"] and, once ACTIVE, execute tools with RUBE_MULTI_EXECUTE_TOOL using discovered slugs and arguments.

Best Practices

Always call RUBE_SEARCH_TOOLS first to get up-to-date tool schemas.
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow rather than creating new ones for each step.

Example Use Cases

Discover a Parma operation tool with RUBE_SEARCH_TOOLS, then execute with RUBE_MULTI_EXECUTE_TOOL using the returned tool_slug.
Establish a Parma connection via RUBE_MANAGE_CONNECTIONS, confirm ACTIVE, and run a batch of tools in a single session.
Iteratively fetch tool schemas via RUBE_SEARCH_TOOLS to adapt to schema changes before running Parma tasks.
Pass memory and exact schema-compliant arguments to each tool slug during RUBE_MULTI_EXECUTE_TOOL.
Handle pagination tokens in RUBE_SEARCH_TOOLS responses to ensure complete tool discovery.

Frequently Asked Questions

Add this skill to your agents