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

agent tool_use skill risk: medium

Booqable Automation via Rube MCP

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

  • External action: high

SKILL 1 file

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

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

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

## Prerequisites

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

### Step 2: Check Connection

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

TOOLS REQUIRED

  • RUBE_SEARCH_TOOLS
  • RUBE_MANAGE_CONNECTIONS
  • RUBE_MULTI_EXECUTE_TOOL
  • RUBE_REMOTE_WORKBENCH
  • RUBE_GET_TOOL_SCHEMAS

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. Generate new ones for new workflows
  9. 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
  • reuse session IDs within a workflow

FAILURE MODES

  • Tool schemas change so never hardcode without searching first
  • Connection not verified as ACTIVE before execution
  • Schema non-compliance with field names/types
  • Missing memory parameter in MULTI_EXECUTE_TOOL
  • Failure to reuse or correctly generate session IDs
  • Incomplete pagination handling

EXAMPLES

Includes multiple example RUBE_* tool calls (SEARCH_TOOLS, MANAGE_CONNECTIONS, MULTI_EXECUTE_TOOL) with sample arguments and session handling.

CAVEATS

Dependencies
  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active Booqable connection via RUBE_MANAGE_CONNECTIONS with toolkit booqable
Missing context
  • Target client or agent environment (e.g., Claude Desktop, Cursor, custom MCP host)
  • Example of a complete end-to-end tool call sequence with realistic values
Ambiguities
  • Placeholder "your specific Booqable task" is mentioned but not illustrated with a concrete example.
  • Session ID handling is described in two slightly different ways across the Tool Discovery and Core Workflow sections.

QUALITY

OVERALL
0.83
CLARITY
0.82
SPECIFICITY
0.88
REUSABILITY
0.78
COMPLETENESS
0.85

IMPROVEMENT SUGGESTIONS

  • Replace the generic placeholder with one or two concrete use-case examples (e.g., "list all rentals" or "create a new customer").
  • Add a minimal working JSON example for RUBE_MULTI_EXECUTE_TOOL that includes realistic arguments and an empty memory object.

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