globalping-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/globalping-automation --openclawGlobalping Automation via Rube MCP
Automate Globalping operations through Composio's Globalping toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/globalping
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Globalping connection via
RUBE_MANAGE_CONNECTIONSwith toolkitglobalping - Always call
RUBE_SEARCH_TOOLSfirst 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_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitglobalping - 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: "Globalping 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 Globalping task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["globalping"]
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_CONNECTIONSshows ACTIVE status before executing tools - Schema compliance: Use exact field names and types from the search results
- Memory parameter: Always include
memoryinRUBE_MULTI_EXECUTE_TOOLcalls, 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 Globalping-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit globalping |
| 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/globalping-automation/SKILL.mdView on GitHub Overview
Automate Globalping operations through Composio's Globalping toolkit using Rube MCP. This skill emphasizes discovering current tool schemas before execution and maintaining an ACTIVE connection to ensure reliable automation. It reduces manual setup and keeps workflows aligned with the latest tool definitions.
How This Skill Works
The automation flow starts by connecting Rube MCP and verifying RUBE_SEARCH_TOOLS to fetch current tool schemas. You then manage the Globalping connection with RUBE_MANAGE_CONNECTIONS and execute discovered tools via RUBE_MULTI_EXECUTE_TOOL using the provided tool_slug and schema-compliant arguments, always including memory. The core pattern is discover → verify connection → execute, reusing sessions when appropriate.
When to Use It
- You need to automate repetitive Globalping tasks without hardcoding tool slugs.
- Tool schemas change and you must fetch the latest inputs before running.
- You want to verify or reestablish a Globalping connection before a workflow.
- Running bulk Globalping operations with multiple tools in sequence.
- Scripting new Globalping tasks that require session reuse across steps.
Quick Start
- Step 1: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm tool schemas are available.
- Step 3: Create a simple workflow: manage a Globalping connection, discover tools, then execute a discovered tool with memory payload.
Best Practices
- Always call RUBE_SEARCH_TOOLS first to get current schemas.
- Check RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing.
- Use exact field names and types from the search results; avoid hardcoding.
- Include memory in RUBE_MULTI_EXECUTE_TOOL calls, even when empty.
- Reuse session IDs for related workflows; generate new ones for new workflows.
Example Use Cases
- Automate a Globalping uptime check across regions using discovered tool slugs.
- Queue multiple Globalping tasks in a single session with RUBE_MULTI_EXECUTE_TOOL.
- Validate and maintain an ACTIVE Globalping connection via RUBE_MANAGE_CONNECTIONS.
- Handle pagination when listing tools via RUBE_SEARCH_TOOLS and continue until complete.
- Bulk-run tools that monitor Globalping endpoints and generate reports.
