Rube MCP is Composio's MCP server used to discover Boloforms tools, manage connections, and execute tools in a regulated workflow.

Do I always need to call RUBE_SEARCH_TOOLS first?

Yes. It fetches current tool schemas which are essential for valid tool selection and argument structures.

How should I structure tool arguments and memory for execution?

Use exact field names and types from the discovered schemas and include a memory object in RUBE_MULTI_EXECUTE_TOOL, even if empty ({}).

boloforms-automation

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

Files (1)

SKILL.md

2.9 KB

Boloforms Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/boloforms

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["boloforms"]
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 Boloforms-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `boloforms`
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/boloforms-automation/SKILL.mdView on GitHub

Overview

Automate Boloforms operations using Composio's Boloforms toolkit via Rube MCP. The skill emphasizes discovering current tool schemas with RUBE_SEARCH_TOOLS before executing workflows and validating the active connection. It helps ensure robust, schema-compliant automation across Boloforms tasks.

How This Skill Works

Connect Rube MCP to the Boloforms toolkit, then verify readiness. Use RUBE_SEARCH_TOOLS to discover available tools, check the connection with RUBE_MANAGE_CONNECTIONS, and finally execute a tool with RUBE_MULTI_EXECUTE_TOOL using the discovered tool slug and schema-aligned arguments, memory, and session_id.

When to Use It

When you need to automate repetitive Boloforms operations end-to-end with up-to-date tool schemas.
When tool schemas change frequently and you must fetch current schemas before running.
When you need to verify Rube MCP and Boloforms connections are ACTIVE prior to execution.
When performing multi-step workflows or bulk operations with RUBE_MULTI_EXECUTE_TOOL.
When you want to reuse session IDs across related workflows to maintain context.

Quick Start

Step 1: Add RUBE MCP endpoint and verify RUBE_SEARCH_TOOLS responds.
Step 2: Discover tools for your Boloforms task with RUBE_SEARCH_TOOLS and capture tool_slug and schemas.
Step 3: Connect and run: RUBE_MANAGE_CONNECTIONS to activate boloforms, then RUBE_MULTI_EXECUTE_TOOL with the chosen tool_slug, proper arguments, memory, and a session_id.

Best Practices

Always call RUBE_SEARCH_TOOLS first to fetch current tool schemas.
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
Use exact field names and types from the discovered schemas.
Include memory in every RUBE_MULTI_EXECUTE_TOOL call, even if empty.
Reuse session IDs for related workflows; generate new ones for new runs and watch for pagination.

Example Use Cases

Automate a daily Boloforms intake by discovering tools and running the appropriate form tool.
Run a multi-tool Boloforms workflow to submit data and trigger post-processing.
Sync Boloforms submissions to an external database, carrying state in memory across steps.
Validate updated tool schemas by re-discovering tools before rerunning a workflow.
Implement a repeatable daily report generation that discovers tools, connects, and executes the required tool(s).

Frequently Asked Questions

Add this skill to your agents