Sms Alert Automation

What This Skill Does

This skill automates SMS Alert operations through Composio's SMS Alert toolkit via Rube MCP. It enables users to programmatically send SMS alerts and notifications for various purposes. This is useful for developers and system administrators.

When to Use

Send SMS alerts for system outages. Notify users of critical updates via SMS. Send appointment reminders via SMS. Send SMS for security alerts. Manage SMS Alert connections. Automate SMS notification workflows.

Key Features

Automates SMS Alert tasks via Rube MCP. Uses Composio's SMS Alert toolkit. Requires an active SMS Alert connection. Discovers available tools using RUBE_SEARCH_TOOLS. Checks connection status via RUBE_MANAGE_CONNECTIONS. Executes tools using RUBE_MULTI_EXECUTE_TOOL.

Prerequisites

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

Step 2: Check Connection

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