eodhd-apis-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/eodhd-apis-automation --openclawEodhd Apis Automation via Rube MCP
Automate Eodhd Apis operations through Composio's Eodhd Apis toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/eodhd_apis
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Eodhd Apis connection via
RUBE_MANAGE_CONNECTIONSwith toolkiteodhd_apis - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkiteodhd_apis - 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: "Eodhd Apis 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 Eodhd Apis task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["eodhd_apis"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Eodhd Apis-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit eodhd_apis |
| 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/eodhd-apis-automation/SKILL.mdView on GitHub Overview
Automate Eodhd Apis operations through Composio's Eodhd Apis toolkit via Rube MCP. It emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before execution and managing connections with RUBE_MANAGE_CONNECTIONS to ensure readiness. Prerequisites include connecting the MCP and enabling the eodhd_apis toolkit.
How This Skill Works
The workflow begins by calling RUBE_SEARCH_TOOLS to fetch available Eodhd Api tool slugs and input schemas. Then you verify the eodhd_apis connection using RUBE_MANAGE_CONNECTIONS and activate it if needed. Finally, you execute one or more tools with RUBE_MULTI_EXECUTE_TOOL, supplying the exact schema-compliant arguments and a memory object, all within a session_id.
When to Use It
- Automating routine Eodhd Apis operations end-to-end via Composio's toolkit.
- When tool schemas change, use RUBE_SEARCH_TOOLS to fetch current slugs and fields.
- When establishing or validating an ACTIVE connection to the eodhd_apis toolkit using RUBE_MANAGE_CONNECTIONS.
- For batch or bulk operations, orchestrate multiple tools with RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH.
- When handling paginated responses, continue fetching until no pagination tokens remain.
Quick Start
- Step 1: RUBE_SEARCH_TOOLS with use_case: 'Eodhd Apis operations' to discover tools.
- Step 2: RUBE_MANAGE_CONNECTIONS to ensure toolkit 'eodhd_apis' is ACTIVE.
- Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug, schema-compliant arguments, memory: {} , and a session_id.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get up-to-date schemas.
- Verify the connection status is ACTIVE via RUBE_MANAGE_CONNECTIONS before running tools.
- Use exact field names and types from the search results; avoid hardcoding tool slugs.
- Always include a memory object in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
- Reuse session IDs within a workflow and handle pagination tokens until completion.
Example Use Cases
- Discover available Eodhd Api tools, pick one, connect, and execute with a single session.
- Connect to eodhd_apis and confirm ACTIVE before running a workflow that updates records.
- Execute a single Eodhd Api operation with the correct tool slug and arguments.
- Run a multi-step workflow that reuses session_id and stores state in memory for successive tools.
- Process a paginated list from an Eodhd Api operation by looping until there are no more pages.
