What prerequisites are required?

Rube MCP must be connected, the dictionary_api toolkit needs an active connection, and you should call RUBE_SEARCH_TOOLS first to obtain current tool schemas.

Why must I always search tools first?

Tool schemas change over time; hardcoding slugs and arguments can break workflows. Searching ensures you use current, valid inputs.

How do I handle pagination?

Check responses for pagination tokens and continue fetching until you receive all pages; ensure your workflow accounts for tokens and continues correctly.

dictionary-api-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

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

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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit dictionary_api
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: "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

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/dictionary-api-automation/SKILL.md

View on GitHub

Overview

This skill automates Dictionary API tasks using Composio's Rube MCP toolkit. It focuses on discovering current tool schemas first, managing connections, and executing dictionary operations reliably.

How This Skill Works

The workflow starts with RUBE_SEARCH_TOOLS to fetch up-to-date Dictionary API tool schemas. It then validates the Dictionary API connection with RUBE_MANAGE_CONNECTIONS and, once ACTIVE, runs the chosen tools using RUBE_MULTI_EXECUTE_TOOL, ensuring the memory payload and session context are included.

When to Use It

When integrating Dictionary API tasks into automated workflows that must adapt to updated tool schemas
When bulk-running dictionary operations with fresh tool slugs from current tool schemas
When establishing or verifying a Dictionary API connection before execution
When implementing multi-step dictionary operations with session reuse across steps
When handling paginated API responses and ensuring complete results

Quick Start

Step 1: RUBE_SEARCH_TOOLS with use_case: 'Dictionary API operations' to discover current tools
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: ['dictionary_api'] and confirm ACTIVE status
Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, proper arguments, memory: {}, and session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before executing to fetch current tool slugs and schemas
Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before running tools
Use exact field names and types from the search results; avoid hardcoding
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty
Reuse session IDs within a workflow and handle pagination tokens when present

Example Use Cases

Discover tools for a batch definition lookup, then execute with a single session_id and the appropriate memory payload
Connect to dictionary_api and run a sequence to fetch definitions and example sentences via discovered tools
Process a long list of terms with pagination, ensuring you continue until all results are retrieved
Reuse a single session across multiple dictionary lookups to improve efficiency
Routinely run RUBE_SEARCH_TOOLS before each major dictionary operation to lock in current slugs

Frequently Asked Questions

Add this skill to your agents