Rube MCP is a central management protocol server used to discover and orchestrate Composio toolkits, including Lmnt.

Do I need to search tools every time?

Yes. Tool schemas can change, so you should call RUBE_SEARCH_TOOLS to obtain current slugs and required inputs before execution.

What if the connection isn’t ACTIVE?

Follow the auth link from RUBE_MANAGE_CONNECTIONS to complete setup, then re-check until the status shows ACTIVE before running tools.

lmnt-automation

Scanned

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

Files (1)

SKILL.md

2.8 KB

Lmnt Automation via Rube MCP

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

Toolkit docs: composio.dev/toolkits/lmnt

Prerequisites

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

Step 2: Check Connection

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

Overview

Automate Lmnt operations through Composio's Lmnt toolkit via Rube MCP. Always search for current tool schemas with RUBE_SEARCH_TOOLS to adapt to changes, then connect and execute validated tools.

How This Skill Works

Connect to Rube MCP and verify RUBE_SEARCH_TOOLS responds to fetch current Lmnt tool schemas. Use the discovered tool slugs and input schemas to run workflows with RUBE_MULTI_EXECUTE_TOOL, ensuring memory is included and the session is managed.

When to Use It

You need up-to-date Lmnt tool schemas before building/adjusting a workflow.
Integrating Lmnt actions into a larger Composio automation pipeline.
Ensuring the Rube MCP connection is ACTIVE before running Lmnt tools.
Discovering tools on-demand to avoid hardcoding slugs and inputs.
Handling large tool lists with pagination and continuing fetch until complete.

Quick Start

Step 1: Verify Rube MCP is connected and RUBE_SEARCH_TOOLS responds.
Step 2: Discover available Lmnt tools with RUBE_SEARCH_TOOLS for your use case.
Step 3: Execute a chosen tool using RUBE_MULTI_EXECUTE_TOOL with the discovered slug and memory, using a session_id.

Best Practices

Always search first with RUBE_SEARCH_TOOLS to get current tool slugs and input schemas.
Check that the connection is ACTIVE using RUBE_MANAGE_CONNECTIONS before executing tools.
Use exact field names and types from the tool schemas when calling tools.
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.

Example Use Cases

Discover available Lmnt tools with RUBE_SEARCH_TOOLS, verify ACTIVE, then execute a discovered tool slug with arguments from the search results.
Automate a multi-step Lmnt operation by discovering tools, validating the connection, and executing a selected tool using RUBE_MULTI_EXECUTE_TOOL.
Reuse a session_id across several Lmnt steps to improve workflow efficiency while maintaining correctness.
When tool slugs or inputs change, re-run RUBE_SEARCH_TOOLS before executing any tool to avoid failures.
Paginate through tool discovery responses to handle large sets of Lmnt operations.

Frequently Asked Questions

Add this skill to your agents