What is represented by RUBE MCP in this context?

RUBE MCP is the Composio Dialpad toolkit integration used to discover, connect, and execute Dialpad tools via the Rube MCP protocol.

Do I need API keys to use this skill?

No. The setup uses an MCP endpoint (e.g., https://rube.app/mcp) and client configuration; no API keys are required.

What should I do if the tool schemas change?

Always call RUBE_SEARCH_TOOLS before executing any workflow to fetch current tool slugs and schemas; do not hardcode slugs or arguments, and ensure memory is included in multi-execute calls.

dialpad-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Dialpad Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/dialpad

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Dialpad operations through Composio's Dialpad toolkit via Rube MCP. Always search tool schemas first to stay current, then connect and execute with the discovered tool slugs.

How This Skill Works

The skill first discovers available Dialpad tools with RUBE_SEARCH_TOOLS, including input schemas. It then checks that the Dialpad connection is ACTIVE using RUBE_MANAGE_CONNECTIONS. Finally, it executes the selected tool via RUBE_MULTI_EXECUTE_TOOL, passing the required arguments and memory payload within a session.

When to Use It

When you need to perform a Dialpad operation after discovering current tool schemas
When you must verify an ACTIVE Dialpad connection before running workflows
When tool schemas must be refreshed to avoid hardcoding slugs or arguments
When performing bulk or sequential Dialpad actions with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
When reusing a session ID across multiple Dialpad steps in a workflow

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client config and verify availability with RUBE_SEARCH_TOOLS
Step 2: Connect to the Dialpad toolkit using RUBE_MANAGE_CONNECTIONS and ensure the status is ACTIVE
Step 3: Discover tools with RUBE_SEARCH_TOOLS and execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL, including a memory payload

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before execution
Use exact field names and types from the tool schemas
Include memory in RUBE_MULTI_EXECUTE_TOOL calls (even if empty {})
Reuse session IDs within a workflow and handle pagination tokens if present

Example Use Cases

Automate creating a Dialpad call by discovering the relevant tool slug and executing it with the required arguments
Check the Dialpad connection status with RUBE_MANAGE_CONNECTIONS before running a workflow
Run a batch of Dialpad actions in a single session using RUBE_MULTI_EXECUTE_TOOL and memory payloads
Bulk operations via RUBE_REMOTE_WORKBENCH and run_composio_tool()
Fetch full tool schemas with RUBE_GET_TOOL_SCHEMAS to adapt your tool calls

Frequently Asked Questions

Add this skill to your agents