Perigon Automation

What This Skill Does

This skill automates Perigon operations through Composio's platform using Rube MCP. It is designed for developers and data analysts who need to integrate financial and market data into their applications. The skill provides tools for discovering available Perigon tools, managing connections, and executing specific data retrieval tasks.

When to Use

• Retrieve real-time stock prices.
• Access historical market data.
• Get financial news and analysis.
• Monitor market trends.
• Automate data feeds for trading algorithms.
• Integrate financial data into reports.

Key Features

• Automates Perigon operations via Rube MCP.
• Uses Composio's Perigon toolkit.
• Discovers tools dynamically using RUBE_SEARCH_TOOLS.
• Manages connections using RUBE_MANAGE_CONNECTIONS.
• Executes tools with RUBE_MULTI_EXECUTE_TOOL.
• Provides documentation for setup and usage.

Manual Installation

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["perigon"] 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

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

Toolkit docs: composio.dev/toolkits/perigon

Prerequisites

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

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["perigon"] 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