Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Dialmycalls Rube MCP Automation Guide

agent tool_use skill risk: high

Dialmycalls Rube MCP Automation Guide

Instructs on automating Dialmycalls operations through Composio's Dialmycalls toolkit via Rube MCP, covering prerequisites, setup steps, tool discovery with RUBE_SEARCH_TOOLS, conn…

  • Human review
  • External action: high

SKILL 1 file

SKILL.md
---
name: dialmycalls-automation
description: "Automate Dialmycalls tasks via Rube MCP (Composio). Always search tools first for current schemas."
---
# Dialmycalls Automation via Rube MCP

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

**Toolkit docs**: [composio.dev/toolkits/dialmycalls](https://composio.dev/toolkits/dialmycalls)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Dialmycalls connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls`
- 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.

1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds
2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls`
3. If connection is not ACTIVE, follow the returned auth link to complete setup
4. Confirm connection status shows ACTIVE before running any workflows

## Tool Discovery

Always discover available tools before executing workflows:

```
RUBE_SEARCH_TOOLS
queries: [{use_case: "Dialmycalls 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 Dialmycalls task"}]
session: {id: "existing_session_id"}
```

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["dialmycalls"]
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 Dialmycalls-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dialmycalls` |
| 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](https://composio.dev)*

REQUIRED CONTEXT

  • Rube MCP connection
  • active dialmycalls connection

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  4. Call RUBE_MANAGE_CONNECTIONS with toolkit dialmycalls
  5. If connection is not ACTIVE, follow the returned auth link to complete setup
  6. Confirm connection status shows ACTIVE before running any workflows
  7. Always discover available tools before executing workflows
  8. Always search first
  9. Check connection
  10. Use exact field names and types from the search results
  11. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  12. Reuse session IDs within a workflow
  13. Generate new session IDs for new workflows
  14. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Schema
table · Operation, Approach
Constraints
  • always search tools first
  • verify active connection before execution
  • use exact schemas from search results

SUCCESS CRITERIA

  • Verify Rube MCP connection via RUBE_SEARCH_TOOLS
  • Ensure dialmycalls connection status is ACTIVE
  • Discover tools via RUBE_SEARCH_TOOLS before execution
  • Use schema-compliant arguments from search results
  • Include memory parameter in execute calls

FAILURE MODES

  • Hardcoding tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  • Executing tools before confirming ACTIVE connection status
  • Omitting the memory parameter in RUBE_MULTI_EXECUTE_TOOL
  • Failing to reuse or correctly manage session IDs

EXAMPLES

Includes examples of RUBE_SEARCH_TOOLS, RUBE_MANAGE_CONNECTIONS, and RUBE_MULTI_EXECUTE_TOOL calls with arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Dialmycalls connection via RUBE_MANAGE_CONNECTIONS
Missing context
  • Target MCP client or environment
  • Example session_id lifecycle
Ambiguities
  • 'your specific Dialmycalls task' used as placeholder without example
  • Quick reference table references RUBE_REMOTE_WORKBENCH and RUBE_GET_TOOL_SCHEMAS without usage details

QUALITY

OVERALL
0.81
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.72
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Replace the placeholder use_case with one or two concrete examples
  • Add a minimal end-to-end example workflow with sample tool slugs and arguments

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT