Skip to main content
Glama
TaylorChen

Multi-MCPs

by TaylorChen

send_sms

Send SMS messages via Twilio integration within the Multi-MCPs server. Specify recipient, sender, and message content to deliver text notifications or alerts.

Instructions

Send an SMS via Twilio

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYes
fromYes
bodyYes

Implementation Reference

  • The asynchronous handler function for the 'send_sms' tool. It validates the input arguments, extracts 'to', 'from', and 'body', and delegates to the Twilio client's sendSms method.
    async send_sms(args: Record<string, unknown>) {
      if (!cfg.twilioAccountSid || !cfg.twilioAuthToken) throw new Error("TWILIO_ACCOUNT_SID/TWILIO_AUTH_TOKEN are not configured");
      const to = String(args.to || "");
      const from = String(args.from || "");
      const body = String(args.body || "");
      if (!to || !from || !body) throw new Error("to, from, body are required");
      return client.sendSms(to, from, body);
    },
  • The input schema for the 'send_sms' tool, specifying an object with required string properties 'to', 'from', and 'body'.
    inputSchema: {
      type: "object",
      properties: { to: { type: "string" }, from: { type: "string" }, body: { type: "string" } },
      required: ["to", "from", "body"],
    },
  • The tool registration object for 'send_sms', including name, description, and input schema, within the registerTwilio function's tools array.
    {
      name: "send_sms",
      description: "Send an SMS via Twilio",
      inputSchema: {
        type: "object",
        properties: { to: { type: "string" }, from: { type: "string" }, body: { type: "string" } },
        required: ["to", "from", "body"],
      },
    },
  • The 'sendSms' helper method in the TwilioClient class that constructs and sends the POST request to Twilio's Messages endpoint.
    sendSms(to: string, from: string, body: string) {
      const form = new URLSearchParams({ To: to, From: from, Body: body });
      return this.request(`/Accounts/${this.accountSid}/Messages.json`, {
        method: "POST",
        headers: { Authorization: `Basic ${this.authHeader}`, "content-type": "application/x-www-form-urlencoded" },
        body: form as any,
      });
    }
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action ('Send') which implies a write/mutation operation, but provides no information about authentication requirements, rate limits, error handling, cost implications, or what happens after sending (e.g., delivery status, response format).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise at just 4 words, front-loading the essential action and service provider. There's zero wasted language, though this conciseness comes at the expense of completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a mutation tool with 3 required parameters, 0% schema coverage, no annotations, and no output schema, the description is severely incomplete. It doesn't address authentication, error cases, response format, or parameter details that are essential for correct tool invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage for all 3 required parameters, the description provides no information about parameter meanings, formats, or constraints. It doesn't explain what 'to' and 'from' represent (phone numbers in specific format), what 'body' contains (message text with length limits), or provide any examples.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('Send') and resource ('SMS via Twilio'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'make_call' or specify what makes SMS distinct from other communication methods in this toolset.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided about when to use this tool versus alternatives like 'make_call' or other communication methods. The description lacks context about appropriate use cases, prerequisites, or limitations for SMS sending.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/TaylorChen/muti-mcps'

If you have feedback or need assistance with the MCP directory API, please join our Discord server