How do I fetch current tool schemas?

Use RUBE_SEARCH_TOOLS with the Ip2whois use case and read the returned tool slugs and input schemas.

What if tool schemas change after I started?

Always search tools first before executing and do not hardcode slugs; ensure the connection is ACTIVE.

ip2whois-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Ip2whois Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/ip2whois

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Ip2whois operations through Composio's Ip2whois toolkit using Rube MCP. Prerequisites require a connected Rube MCP with RUBE_SEARCH_TOOLS available and an active Ip2whois connection via RUBE_MANAGE_CONNECTIONS. Always search for current schemas before execution to ensure up to date tool slugs and input fields.

How This Skill Works

Connect to Rube MCP and verify tool schemas by running RUBE_SEARCH_TOOLS. Establish or confirm the Ip2whois toolkit connection with RUBE_MANAGE_CONNECTIONS, then execute a discovered tool via RUBE_MULTI_EXECUTE_TOOL using the exact input fields and a memory payload. Reuse a session ID within workflows to speed up executions and maintain context.

When to Use It

Automating Ip2whois operations at scale by chaining multiple lookups using discovered tool slugs.
When tool schemas change, fetch current slugs and inputs with RUBE_SEARCH_TOOLS before running.
When setting up a new Ip2whois workflow, verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
For bulk Ip2whois tasks, orchestrate many tool executions with RUBE_MULTI_EXECUTE_TOOL using a shared session.
When debugging, follow the known pitfalls to avoid hardcoding slugs or claims and to confirm active connections.

Quick Start

Step 1: Verify Rube MCP is configured and reachable.
Step 2: Run RUBE_SEARCH_TOOLS to fetch current Ip2whois tool slugs and input schemas.
Step 3: Use RUBE_MANAGE_CONNECTIONS to activate the ip2whois toolkit and then run RUBE_MULTI_EXECUTE_TOOL with memory {} and your session.

Best Practices

Always search tools first to get current schemas.
Check that RUBE_MANAGE_CONNECTIONS reports ACTIVE before executing tools.
Use exact field names and types from the search results.
Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty.
Reuse session IDs within a workflow and generate new ones for new workflows.

Example Use Cases

Discover Ip2whois tools and run a lookup for 8.8.8.8 using the discovered tool slug.
Set up the ip2whois connection and perform the first lookup after confirming ACTIVE status.
Update an automation when a tool schema changes and re run with the new slug.
Execute a batch of IP lookups by looping RUBE_MULTI_EXECUTE_TOOL calls with the same session.
Debug a failed run by rechecking schemas and connection status per the pitfalls.

Frequently Asked Questions

Add this skill to your agents