Skip to main content
Glama

sms

Send text messages via SMS or WhatsApp to any phone number in E.164 format. Specify the message and optionally choose the delivery channel.

Instructions

Send an SMS or WhatsApp message. Cost: 1 credit.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toYesPhone number in E.164 format (e.g. +1234567890)
messageYesMessage text
channelNoauto, sms, or whatsappauto

Implementation Reference

  • Schema definition for the 'sms' tool: defines name, description, and input parameters (to, message, channel).
    {
      name: "sms",
      description: "Send an SMS or WhatsApp message. Cost: 1 credit.",
      inputSchema: {
        to: z.string().describe("Phone number in E.164 format (e.g. +1234567890)"),
        message: z.string().describe("Message text"),
        channel: z.string().optional().default("auto").describe("auto, sms, or whatsapp"),
      },
    },
  • src/index.ts:247-259 (registration)
    Registration of all capabilities (including 'sms') as MCP tools via server.registerTool in a loop.
    for (const cap of CAPABILITIES) {
      // Cast inputSchema to avoid TS2589 (excessively deep type instantiation from Zod chains)
      server.registerTool(
        cap.name,
        {
          description: cap.description,
          inputSchema: cap.inputSchema as any,
        },
        async (args: any): Promise<CallToolResult> => {
          return callSuprsonic(cap.name, args as Record<string, unknown>);
        },
      );
    }
  • Generic HTTP handler (callSuprsonic) used by the 'sms' tool and all other tools. Makes a POST request to the Suprsonic API with the capability name and parameters.
    async function callSuprsonic(capability: string, params: Record<string, unknown>): Promise<CallToolResult> {
      if (!API_KEY) {
        return {
          content: [{ type: "text", text: "Error: SUPRSONIC_API_KEY environment variable is not set. Get your key at https://suprsonic.ai/app/apis" }],
          isError: true,
        };
      }
    
      try {
        const resp = await fetch(`${BASE_URL}/v1/agent`, {
          method: "POST",
          headers: {
            "Authorization": `Bearer ${API_KEY}`,
            "Content-Type": "application/json",
          },
          body: JSON.stringify({ capability, params }),
        });
    
        const result = await resp.json() as any;
    
        // Handle non-envelope responses (401, 429, etc. return {"detail": ...})
        if (result.detail && result.success === undefined) {
          const msg = typeof result.detail === "object" ? (result.detail.title || result.detail.detail || JSON.stringify(result.detail)) : String(result.detail);
          return {
            content: [{ type: "text", text: `Error (HTTP ${resp.status}): ${msg}` }],
            isError: true,
          };
        }
    
        if (!result.success) {
          const errMsg = result.error?.detail || result.error?.title || "Request failed";
          return {
            content: [{ type: "text", text: `Error: ${errMsg}` }],
            isError: true,
          };
        }
    
        const text = JSON.stringify(result.data, null, 2);
        const meta = result.metadata
          ? `\n\n[Provider: ${(result.metadata as any).provider_used || "unknown"}, ${(result.metadata as any).response_time_ms || 0}ms, ${result.credits_used || 0} credits]`
          : "";
    
        return {
          content: [{ type: "text", text: text + meta }],
        };
      } catch (err) {
        return {
          content: [{ type: "text", text: `Network error: ${err instanceof Error ? err.message : String(err)}` }],
          isError: true,
        };
      }
    }
Behavior2/5

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

No annotations provided, so description carries full burden. It only adds cost information ('1 credit') but omits behavioral traits like rate limits, authentication requirements, error handling, or success/failure responses. Minimal disclosure beyond what the schema already offers.

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?

Two sentences effectively convey purpose and cost. No wasted words; front-loaded with essential information. Exemplary conciseness.

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?

No output schema; description missing behavioral details such as response format, error states, or asynchronous behavior. While simple, the tool lacks completeness for an agent to understand full implications of invocation.

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

Parameters3/5

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

Schema description coverage is 100%, so baseline is 3. The description does not add additional meaning to parameters beyond what schema already states (phone format, message text, channel options).

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

Purpose5/5

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

Description uses specific verb 'Send' and resource 'SMS or WhatsApp message', clearly distinguishing it from siblings which handle emails, images, documents, etc. Cost info adds specificity.

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

Usage Guidelines4/5

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

The description clearly indicates the tool is for sending SMS or WhatsApp messages. It does not explicitly exclude alternatives but given sibling tools are for vastly different purposes, the context is clear. Lacks explicit when-not-to-use guidance.

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/O-mega-Enterprise/suprsonic-mcp'

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