Get the FREE Ultimate OpenClaw Setup Guide →

radar-automation

Scanned
npx machina-cli add skill ComposioHQ/awesome-claude-skills/radar-automation --openclaw
Files (1)
SKILL.md
2.8 KB

Radar Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/radar

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["radar"]
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

OperationApproach
Find toolsRUBE_SEARCH_TOOLS with Radar-specific use case
ConnectRUBE_MANAGE_CONNECTIONS with toolkit radar
ExecuteRUBE_MULTI_EXECUTE_TOOL with discovered tool slugs
Bulk opsRUBE_REMOTE_WORKBENCH with run_composio_tool()
Full schemaRUBE_GET_TOOL_SCHEMAS for tools with schemaRef

Powered by Composio

Source

git clone https://github.com/ComposioHQ/awesome-claude-skills/blob/master/composio-skills/radar-automation/SKILL.mdView on GitHub

Overview

Radar Automation via Rube MCP enables orchestration of Radar workflows through Composio's Radar toolkit. It hinges on an active Rube MCP connection and up-to-date tool schemas fetched with RUBE_SEARCH_TOOLS. Always discover tools before running workflows to avoid stale slugs and mismatched inputs.

How This Skill Works

The skill discovers available Radar tools and their input schemas by calling RUBE_SEARCH_TOOLS, then verifies the Radar connection with RUBE_MANAGE_CONNECTIONS. Once active, it executes the chosen tool via RUBE_MULTI_EXECUTE_TOOL using the required arguments and memory, keyed to a session.

When to Use It

  • Initial Radar workflow setup with up-to-date tool schemas
  • Verifying Rube MCP connection before running Radar tasks
  • Discovering available Radar tools for a use case
  • Executing a discovered Radar tool with correct arguments
  • Managing multi-step Radar workflows with session reuse and pagination

Quick Start

  1. Step 1: Configure Rube MCP (https://rube.app/mcp) as an MCP server and verify RUBE_SEARCH_TOOLS
  2. Step 2: Discover tools with RUBE_SEARCH_TOOLS for your Radar use_case and start a session
  3. Step 3: Check connection with RUBE_MANAGE_CONNECTIONS and execute a tool using RUBE_MULTI_EXECUTE_TOOL with memory and the session_id

Best Practices

  • Always run RUBE_SEARCH_TOOLS first to fetch current schemas
  • Verify ACTIVE status in RUBE_MANAGE_CONNECTIONS before execution
  • Use exact field names/types from search results
  • Include memory in RUBE_MULTI_EXECUTE_TOOL payload, even if empty
  • Reuse session IDs within a workflow and handle pagination tokens

Example Use Cases

  • Automating Radar device status checks by discovering tools and executing the appropriate one with the latest schema
  • Orchestrating a multi-step Radar diagnostic plan using a single reusable session
  • Fetching Radar sensor data by discovering a relevant tool and executing with precise inputs
  • Validating the Radar connection before launching bulk operations
  • Iteratively listing tools with pagination and running a workflow on the required tool

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers