Skip to main content
Glama

SMS

sms

Send SMS or WhatsApp messages. Default channel is SMS (reliable delivery). WhatsApp requires recipient opt-in: they must have messaged your Business number within 24 hours. Returns the message id, channel, recipient, sender number and send status. Sends a real message to a phone number: a sent message cannot be recalled, and every call sends a new one. Use it to text a number the user gave you. Cost: 1 credit, charged only when a call succeeds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "to": "<to>",
      "message": "<message>"
    },
    "name": "sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPhone number in E.164 form: a + and the country code first. Spaces, dashes and brackets are dropped.
channelNoDelivery channel. Auto sends via SMS. WhatsApp requires opt-in: recipient must have messaged your Business number in the last 24 hours, otherwise the message is silently dropped by Meta.auto
messageYesMessage text: at most 1,600 characters for SMS, 4,096 for WhatsApp.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / message / description
      Previous value: -"Message text."New value: +"Message text: at most 1,600 characters for SMS, 4,096 for WhatsApp."
    • changedInput schema / properties / to / description
      Previous value: -"Phone number (E.164)."New value: +"Phone number in E.164 form: a + and the country code first. Spaces, dashes and brackets are dropped."
  2. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: messages cannot be recalled, every call sends a new message, WhatsApp messages are silently dropped without opt-in, and cost is 1 credit charged only on success. It also lists return fields (message id, channel, recipient, sender, status) despite no output schema. This is exactly the missing-context layer annotations can't convey.

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?

Five short sentences, front-loaded with the action and channel default, then the irreversible-send warning, then cost and return values. Every sentence contributes a fact an agent needs before calling.

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

Completeness5/5

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

Covers action, channel semantics, recipient requirements, irreversibility, billing, and return payload for a 3-param tool with no output schema. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3. The description adds real value by clarifying that the default 'auto' channel resolves to SMS (reliable delivery) and reiterating the WhatsApp opt-in consequence (silent drop), which the schema mentions more briefly.

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?

First sentence states the exact verb and resource ('Send SMS or WhatsApp messages') and immediately disambiguates the channel choice. An agent can distinguish this from siblings like emails or tts without opening the schema.

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?

'Use it to text a number the user gave you' gives a clear usage condition, and the WhatsApp 24-hour opt-in rule acts as an explicit exclusion for that channel. It stops short of naming alternative tools or stating when not to message at all, so it falls just below a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.