What is Rube MCP in this context?

Rube MCP is Composio's MCP server that provides ready tool schemas for Fullenrich; you should connect and use RUBE_SEARCH_TOOLS to fetch schemas.

Why must I always search tools first?

Tool schemas change; hardcoding slugs/arguments leads to failures; dynamic search ensures you have current input schemas and recommended execution plans.

What should I do if the connection is not ACTIVE?

Check ACTIVE status using RUBE_MANAGE_CONNECTIONS, complete the authentication flow using the provided link, then retry until ACTIVE before executing workflows.

fullenrich-automation

Scanned

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

Files (1)

SKILL.md

2.9 KB

Fullenrich Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/fullenrich

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Fullenrich operations through Composio's Fullenrich toolkit via Rube MCP. It emphasizes always searching for current tool schemas with RUBE_SEARCH_TOOLS before execution and requires a connected Rube MCP and an active Fullenrich connection. The workflow covers discovery, connection verification, and executing tools with the correct memory and session handling.

How This Skill Works

First, discover available Fullenrich tools with RUBE_SEARCH_TOOLS using the Fullenrich use case. Then verify the connection with RUBE_MANAGE_CONNECTIONS and finally run tools via RUBE_MULTI_EXECUTE_TOOL, supplying the discovered tool_slug, proper arguments, and a memory object. The process enforces using current schemas and reusing sessions to maintain workflow continuity.

When to Use It

When you need to run a Fullenrich workflow but want to ensure you have the latest tool schemas before execution
When setting up a new Fullenrich integration and need to authenticate and activate the connection
When executing a sequence of Fullenrich tools in a single process, reusing a session
When a workflow requires handling dynamic inputs or pagination in tool responses
When performing bulk operations via Composio's Fullenrich toolkit

Quick Start

Step 1: Add https://rube.app/mcp as an MCP server in your client configuration (no API keys needed)
Step 2: Verify RUBE_SEARCH_TOOLS responds to confirm MCP connectivity and tool schemas are available
Step 3: Call RUBE_MANAGE_CONNECTIONS with toolkit fullenrich and ensure the connection is ACTIVE before executing workflows

Best Practices

Always search for current tool schemas before executing
Check that RUBE_MANAGE_CONNECTIONS shows ACTIVE before running 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; generate new ones for new workflows

Example Use Cases

Discover tools for a data enrichment task, connect to Fullenrich, then execute a matching tool slug with proper args
Set up a new Fullenrich connection, verify ACTIVE, and run the first enrichment workflow
Execute multiple Fullenrich tools in sequence using the same session_id
Handle a tool that requires pagination tokens and fetch all results before proceeding
Run bulk Fullenrich tasks via RUBE_REMOTE_WORKBENCH with run_composio_tool

Frequently Asked Questions

Add this skill to your agents