Radar Automation

What This Skill Does

This skill automates Radar operations using the Composio's Radar toolkit via Rube MCP. It helps users streamline Radar tasks by discovering available tools, checking connections, and executing specific workflows. It is designed for users who want to integrate Radar with other systems and automate location tracking and geofencing processes.

When to Use

Automate geofence creationTrack user locationAnalyze location dataTrigger actions based on locationManage Radar connectionsDynamically update geofences

Key Features

Uses Rube MCP for Radar automation. Requires an active Radar connection. Employs RUBE_SEARCH_TOOLS for tool discovery. Utilizes RUBE_MANAGE_CONNECTIONS for connection management. Executes tools with RUBE_MULTI_EXECUTE_TOOL. Provides a structured workflow pattern.

Manual Installation

Manual installationView Full Skill ContentThe complete markdown content that gets installedRadar 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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit radar 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: "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

Powered by Composio