Do I need an active Rube MCP connection before running Bolt IoT tools?

Yes. Ensure RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing any Bolt IoT tool to avoid failed operations.

Why must I search tools first?

Tool schemas change over time. Always calling RUBE_SEARCH_TOOLS ensures you use current slugs and correct argument names instead of hardcoding.

What should memory contain in RUBE_MULTI_EXECUTE_TOOL calls?

Include a memory object (even if empty like {}) to preserve context across tool executions within a session.

bolt-iot-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Bolt Iot Automation via Rube MCP

Automate Bolt Iot operations through Composio's Bolt Iot toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/bolt_iot

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Bolt IoT operations using Composio's Bolt IoT toolkit via Rube MCP. The workflow centers on discovering current tool schemas with RUBE_SEARCH_TOOLS, validating an ACTIVE Bolt IoT connection, and executing discovered tools with RUBE_MULTI_EXECUTE_TOOL.

How This Skill Works

Technically, you first discover the available Bolt IoT tools with RUBE_SEARCH_TOOLS for your task. Then you verify the connection status with RUBE_MANAGE_CONNECTIONS and finally execute the chosen tool using RUBE_MULTI_EXECUTE_TOOL, supplying the exact arguments, memory, and a valid session_id.

When to Use It

Automating Bolt IoT operations where tool schemas must be current
When your workflow requires a verified ACTIVE connection before tool execution
When you need to run a tool using the discovered slug rather than hardcoding it
During bulk or batched Bolt IoT tasks using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH
When you want to reuse session IDs for a consistent workflow

Quick Start

Step 1: RUBE_SEARCH_TOOLS with queries: [{use_case: Bolt IoT operations, known_fields: none}] and session: {generate_id: true}
Step 2: RUBE_MANAGE_CONNECTIONS with toolkits: [bolt_iot], session_id: your_session_id
Step 3: RUBE_MULTI_EXECUTE_TOOL with the discovered tool_slug from search results; supply arguments from the search results; memory: {}; session_id: your_session_id

Best Practices

Always run RUBE_SEARCH_TOOLS before executing to get current tool slugs and schemas
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before any execution
Use exact field names and types from the search results; do not hardcode
Always include a memory object in RUBE_MULTI_EXECUTE_TOOL, even if empty
Reuse session IDs within a workflow and generate new IDs for new workflows

Example Use Cases

Discover and run a Bolt IoT operation by querying with RUBE_SEARCH_TOOLS for a specific use case and executing a returned tool slug with RUBE_MULTI_EXECUTE_TOOL
Establish and maintain an ACTIVE Bolt IoT connection via RUBE_MANAGE_CONNECTIONS before performing a device action
Update firmware on multiple Bolt IoT devices by selecting the firmware_update tool slug from search results and providing device_ids
Read sensor data after confirming the required tool schemas are available and the connection is active
Batch several Bolt IoT actions in a single workflow using RUBE_MULTI_EXECUTE_TOOL or RUBE_REMOTE_WORKBENCH

Frequently Asked Questions

Add this skill to your agents