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

agent tool_use skill risk: low

Dictionary API Automation via Rube MCP

Instructs on automating Dictionary API operations through Composio's Dictionary API toolkit using Rube MCP, including prerequisites, setup steps, tool discovery with RUBE_SEARCH_TO…

  • External action: medium

SKILL 1 file

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

Automate Dictionary API operations through Composio's Dictionary API toolkit via Rube MCP.

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

## Prerequisites

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

### Step 2: Check Connection

```
RUBE_MANAGE_CONNECTIONS
toolkits: ["dictionary_api"]
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 Dictionary API-specific use case |
| Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `dictionary_api` |
| 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 availability
  • Dictionary API toolkit connection status
  • specific Dictionary API use case

OPTIONAL CONTEXT

  • existing session_id
  • pagination tokens

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_GET_TOOL_SCHEMAS
  • RUBE_REMOTE_WORKBENCH

ROLES & RULES

  1. Always search tools first for current schemas
  2. Always call RUBE_SEARCH_TOOLS first to get current tool schemas
  3. Always discover available tools before executing workflows
  4. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  5. Confirm connection status shows ACTIVE before running any workflows
  6. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  7. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  8. Use exact field names and types from the search results
  9. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty
  10. Reuse session IDs within a workflow
  11. Generate new session IDs for new workflows
  12. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
markdown
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results
  • include memory parameter even if empty

SUCCESS CRITERIA

  • Always search first
  • Check connection status is ACTIVE
  • Use schema-compliant arguments from search results
  • Include memory parameter in execute calls
  • Reuse session IDs appropriately

FAILURE MODES

  • Hardcoding tool slugs or arguments without searching first
  • Executing tools without ACTIVE connection
  • Using incorrect field names or types
  • Omitting the memory parameter
  • Failing to handle pagination

CAVEATS

Dependencies
  • Requires RUBE_SEARCH_TOOLS available
  • Requires active Dictionary API connection via RUBE_MANAGE_CONNECTIONS
  • Requires Rube MCP server added at https://rube.app/mcp
Missing context
  • Concrete example workflows with full argument values
  • Target client or environment for MCP configuration
Ambiguities
  • Placeholder text 'your specific Dictionary API task' is not illustrated with an example substitution

QUALITY

OVERALL
0.79
CLARITY
0.88
SPECIFICITY
0.78
REUSABILITY
0.72
COMPLETENESS
0.82

IMPROVEMENT SUGGESTIONS

  • Replace inline placeholders with explicit template variables such as {{use_case}}
  • Add 2-3 complete worked examples showing end-to-end tool calls and responses

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