Skip to main content
Glama

Spoof Caller ID

Send SMS

send_sms

Sends one SMS with your sender ID. COSTS MONEY: the route price per part for the destination is taken from the balance. Without "route" the cheapest priced route is used; get route ids and prices from list_sms_routes.

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>",
      "text": "<text>",
      "sender_id": "<sender_id>"
    },
    "name": "send_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPhone number in international format, e.g. +447700900123
textYesMessage text (160 GSM-7 characters per part, 70 with Unicode)
routeNoRoute id from list_sms_routes (optional)
countryNoISO code of the destination when the number has no + prefix (optional)
sender_idYesSender name or number shown to the recipient (up to 11 letters/digits)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare the write/open-world/non-idempotent profile, and the description adds the critical non-obvious trait: this call debits the account balance at the per-part route price. It does not cover what is returned (message id, part count, actual charged amount) or how partial failures behave.

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?

Three tight sentences, each doing work: action and scope first, then the money warning, then route defaulting plus the pointer to list_sms_routes. The cost warning is capitalized and front-loaded where an agent will not miss it.

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

Completeness3/5

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

Covers the decision-relevant behavior for a paid send, but with no output schema the description should say what a successful send returns (message id, parts, charged amount) and whether delivery is asynchronous — information an agent needs to report results or verify a send.

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, but the description adds real meaning about the optional "route" parameter — omitting it selects the cheapest priced route, and prices come from list_sms_routes. That default-resolution behavior is not stated anywhere in the schema.

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?

States a specific verb and resource with scope: "Sends one SMS with your sender ID." An agent can tell instantly this is the single-message send operation rather than a listing or lookup tool, and it is clearly differentiated from list_sms_routes and the account/voice siblings.

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?

Gives concrete operational context: sends require a sender ID, incur a per-part charge against the balance, and route selection only needs list_sms_routes when a specific route is wanted. It stops short of explicit when-not-to-use guidance (e.g. don't use for bulk, don't resend on ambiguous failures).

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.

Resources