What is required to start?

A connected Rube MCP (https://rube.app/mcp), RUBE_SEARCH_TOOLS response for Ip2location IO tools, and an ACTIVE RUBE_MANAGE_CONNECTIONS for ip2location_io.

Why is 'Always search first' emphasized?

Tool schemas change frequently; this avoids hardcoding slugs and args and ensures compatibility.

How do I handle multiple tools in one workflow?

Reuse the same session_id across calls, pass memory in RUBE_MULTI_EXECUTE_TOOL, and call RUBE_REMOTE_WORKBENCH if doing bulk tasks.

ip2location-io-automation

Scanned

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

Files (1)

SKILL.md

3.0 KB

Ip2location IO Automation via Rube MCP

Automate Ip2location IO operations through Composio's Ip2location IO toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/ip2location_io

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS
toolkits: ["ip2location_io"]
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 Ip2location IO-specific use case
Connect	`RUBE_MANAGE_CONNECTIONS` with toolkit `ip2location_io`
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/ip2location-io-automation/SKILL.md

View on GitHub

Overview

This skill automates Ip2location IO operations through Composio's Ip2location IO toolkit using Rube MCP. It emphasizes always searching for current tool schemas with RUBE_SEARCH_TOOLS and verifying an ACTIVE connection via RUBE_MANAGE_CONNECTIONS before execution. It streamlines end-to-end workflows from discovery to multi-tool execution.

How This Skill Works

First, discover available Ip2location IO tools with RUBE_SEARCH_TOOLS and the use_case you need. Then verify or establish an ACTIVE connection with RUBE_MANAGE_CONNECTIONS for the ip2location_io toolkit. Finally, execute the chosen tool(s) with RUBE_MULTI_EXECUTE_TOOL, supplying the schema-compliant arguments and a memory payload; include the session_id and reuse sessions when possible.

When to Use It

When you need to automate repeated Ip2location IO tasks and want up-to-date tool schemas
When setting up a new Ip2location IO workflow and need to discover tool slugs first
When validating the active connection before running workflows
When performing multi-tool or batch Ip2location IO operations in a single session
When troubleshooting or updating tool schemas due to changes in Ip2location IO workflows

Quick Start

Step 1: Ensure Rube MCP is connected and RUBE_SEARCH_TOOLS returns Ip2location IO tools
Step 2: Use RUBE_MANAGE_CONNECTIONS with toolkit ip2location_io and verify ACTIVE status
Step 3: Execute a discovered tool with RUBE_MULTI_EXECUTE_TOOL, providing memory and a session_id

Best Practices

Always call RUBE_SEARCH_TOOLS before running tools
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE status before executing
Use exact field names and types from search results
Include memory payload in RUBE_MULTI_EXECUTE_TOOL calls (even if empty)
Reuse session IDs within a workflow; regenerate for new tasks and watch for pagination

Example Use Cases

Run a single IP geolocation lookup by discovering the tool slug and executing it with an IP address
Run a batch geolocation for a list of IPs after establishing an ACTIVE ip2location_io connection
Validate connection and then execute multiple tools in one session using RUBE_MULTI_EXECUTE_TOOL
Bulk IP lookups using RUBE_REMOTE_WORKBENCH and a run_composio_tool wrapper
Inspect and adapt to new tool schemas by querying RUBE_GET_TOOL_SCHEMAS before updating workflows

Frequently Asked Questions

Add this skill to your agents