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

agent tool_use skill risk: medium

Algodocs Automation via Rube MCP

Guides automation of Algodocs operations through Composio's Algodocs toolkit using Rube MCP, covering prerequisites, setup, tool discovery with RUBE_SEARCH_TOOLS, connection manage…

  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

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

OPTIONAL CONTEXT

  • existing session_id
  • specific Algodocs task use case

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. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS
  5. Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools
  6. Use exact field names and types from the search results
  7. Always include memory in RUBE_MULTI_EXECUTE_TOOL calls even if empty
  8. Reuse session IDs within a workflow
  9. Generate new session IDs for new workflows
  10. Check responses for pagination tokens and continue fetching until complete

EXPECTED OUTPUT

Format
plain_text
Constraints
  • always call RUBE_SEARCH_TOOLS first
  • verify ACTIVE connection before execution
  • use exact schemas from search results

FAILURE MODES

  • Never search first so tool schemas are outdated
  • Skip connection status check before executing tools
  • Fail to use exact schema field names and types
  • Omit memory parameter from RUBE_MULTI_EXECUTE_TOOL
  • Reuse session IDs across different workflows

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Algodocs connection via RUBE_MANAGE_CONNECTIONS with toolkit algodocs
Missing context
  • Concrete example task descriptions for the use_case queries
  • Error handling or retry logic for failed tool executions
Ambiguities
  • Session management instructions mix 'generate_id: true' and 'id: existing_session_id' without clarifying when each applies.
  • Does not specify output format or length expected from the automation workflows.

QUALITY

OVERALL
0.78
CLARITY
0.78
SPECIFICITY
0.82
REUSABILITY
0.80
COMPLETENESS
0.72

IMPROVEMENT SUGGESTIONS

  • Add one or two fully-worked example workflows with sample RUBE_SEARCH_TOOLS queries and resulting tool calls.

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