google-address-validation-automation
Scannednpx machina-cli add skill ComposioHQ/awesome-claude-skills/google-address-validation-automation --openclawGoogle Address Validation Automation via Rube MCP
Automate Google Address Validation operations through Composio's Google Address Validation toolkit via Rube MCP.
Toolkit docs: composio.dev/toolkits/google_address_validation
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Google Address Validation connection via
RUBE_MANAGE_CONNECTIONSwith toolkitgoogle_address_validation - 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 toolkitgoogle_address_validation - 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: "Google Address Validation 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 Google Address Validation task"}]
session: {id: "existing_session_id"}
Step 2: Check Connection
RUBE_MANAGE_CONNECTIONS
toolkits: ["google_address_validation"]
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 Google Address Validation-specific use case |
| Connect | RUBE_MANAGE_CONNECTIONS with toolkit google_address_validation |
| 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/google-address-validation-automation/SKILL.mdView on GitHub Overview
Automate Google Address Validation tasks using Composio's Google Address Validation toolkit via Rube MCP. Start by ensuring Rube MCP is connected, the google_address_validation toolkit is ACTIVE, and always search for current tool schemas before running workflows.
How This Skill Works
The workflow discovers available tools with RUBE_SEARCH_TOOLS, then confirms the google_address_validation connection via RUBE_MANAGE_CONNECTIONS, and finally executes the chosen tool through RUBE_MULTI_EXECUTE_TOOL. Always pass a memory payload (even if empty) and reuse session IDs to maintain continuity across steps.
When to Use It
- Batch-validate a list of customer addresses from a CRM or CSV using up-to-date tool schemas.
- Integrate Google Address Validation checks into an automated data-cleaning pipeline.
- Validate addresses in nightly ETL jobs while adapting to schema changes by re-discovering tools first.
- Verify connections and run tools in environments where API keys are not used but a gateway via Rube MCP is available.
- Perform bulk or remote execution with run_composio_tool when orchestrating multiple tool invocations.
Quick Start
- Step 1: Configure RUBE MCP by adding https://rube.app/mcp as an MCP server in your client.
- Step 2: Run RUBE_SEARCH_TOOLS to discover current google_address_validation tools and schemas.
- Step 3: Run RUBE_MANAGE_CONNECTIONS to activate the toolkit, then execute a chosen tool with RUBE_MULTI_EXECUTE_TOOL using the memory payload.
Best Practices
- Always run RUBE_SEARCH_TOOLS first to fetch current tool slugs and schemas.
- Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE before executing tools.
- Use exact field names and types from the search results; do not hardcode schemas.
- Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({ }).
- Reuse session IDs within a workflow and generate new ones for new workflows; monitor pagination tokens.
Example Use Cases
- Validate 500 addresses from a CRM export and write normalized results back to the database.
- Nightly data-cleansing job that auto-discovers and runs tools against new address data.
- CRM ingestion pipeline that validates addresses before import.
- Demo workflow showing RUBE_SEARCH_TOOLS and RUBE_MULTI_EXECUTE_TOOL in action.
- Handle schema changes by re-discovering tools prior to execution and adapting requests accordingly.
