Skip to main content
Glama

Sparetext

Send a text

send_sms
Destructive

Send an SMS from the user's own number to one or more people. Returns each text's id; status starts as queued. Confirm the recipients and exact wording with the user first, unless they gave both. One SMS holds 160 GSM-7 characters (153 per segment when longer); an emoji or any character outside GSM-7 makes it UCS-2: 70 characters (67 per segment). Each segment is billed. For person-to-person texts only: carriers filter bulk and marketing (A2P) traffic on personal numbers.

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

Input Schema

NameRequiredDescriptionDefault
toYesRecipients, up to 100
simNoOptional, Android only: which SIM sends it, numbered as on the phone (1 or 2). list_devices shows each phone's SIMs. Defaults to the SIM chosen in the app.
textNoThe message, up to 1,600 characters (may be empty when media_urls has a picture)
varsNoWith template_id: the blanks, like {"time": "7 pm"}. A connection limited to templates fills each with at most 40 characters on one line, no link, and sends no pictures.
urgentNoOptional: for a one-time code or anything time-critical. It goes ahead of other waiting texts; with ttl_seconds of 900 or less it also skips the phone's sending hours and caps.
send_atNoOptional: send later (ISO 8601, up to 30 days ahead).
device_idNoOptional: which phone sends it (see list_devices). Defaults to the default phone.
expires_atNoOptional, instead of ttl_seconds: the same as an ISO 8601 time.
media_urlsNoOptional: up to 3 pictures (JPEG, PNG or GIF, public https URLs, 5 MB each) to send as an MMS. Android 1.4.0 or the Mac relay. text may then be empty.
template_idNoOptional, instead of text: a saved template's id (see list_templates). Its blanks are filled from vars; {{name}} also from the person's contact name.
ttl_secondsNoOptional: if it hasn't gone out this many seconds after it may (send_at, or now), drop it and never send it; it fails with error expired. Use for one-time codes and anything that stops mattering, e.g. 300.

Output Schema

NameRequiredDescriptionDefault
smsYes
noteNo
deviceYes
batchIdYes
messagesYes
estimatedCompletionAtNoAbout when the last text goes out

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / vars / description
      Previous value: -"With template_id: the blanks, like {\"time\": \"7 pm\"}."New value: +"With template_id: the blanks, like {\"time\": \"7 pm\"}. A connection limited to templates fills each with at most 40 characters on one line, no link, and sends no pictures."
  2. Changed5 schema fields changed
    • addedInput schema / properties / template_id
      Added value: +{
      +  "description": "Optional, instead of text: a saved template's id (see list_templates). Its blanks are filled from vars; {{name}} also from the person's contact name.",
      +  "type": "string"
      +}
    • addedInput schema / properties / urgent
      Added value: +{
      +  "description": "Optional: for a one-time code or anything time-critical. It goes ahead of other waiting texts; with ttl_seconds of 900 or less it also skips the phone's sending hours and caps.",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / vars
      Added value: +{
      +  "additionalProperties": {
      +    "type": "string"
      +  },
      +  "description": "With template_id: the blanks, like {\"time\": \"7 pm\"}.",
      +  "type": "object"
      +}
    • changedInput schema / required
      Previous value: -[
      -  "to",
      -  "text"
      -]New value: +[
      +  "to"
      +]
    • addedOutput schema / properties / estimatedCompletionAt
      Added value: +{
      +  "description": "About when the last text goes out",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  3. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Goes well past the annotations (destructive/openWorld/non-idempotent) by disclosing the response shape ('Returns each text's id; status starts as queued'), the billing model ('Each segment is billed'), and the delivery guarantee for ttl_seconds ('drop it and never send it; it fails with error expired'). The carrier-filtering warning is behavior an agent could not infer from any structured field.

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

Conciseness4/5

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

Front-loads the core action and the confirmation requirement before the technical encoding detail. The SMS-segmentation sentences are dense but each carries decision-relevant information; only the segment-billing aside borders on redundant restatement of the encoding rule.

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?

For an 11-parameter, nested, open-world destructive tool with an output schema present, the description covers action, prerequisites, cost, timing/expiry semantics and eligibility limits. Nothing an agent needs to decide whether and how to call it is missing, and return values are correctly left to the output schema.

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 genuinely informs how to populate `text`: 160 GSM-7 characters vs 153 per segment, and the UCS-2 penalty for emoji, which explains the 1,600-character schema cap. It does not add much for the remaining ten parameters, whose meaning is already in the schema.

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?

States a specific verb and resource ('Send an SMS from the user's own number') plus the fan-out shape ('to one or more people'), which is clear on its own. It never distinguishes itself from the sibling send_sms_batch, however, and with 100 recipients allowed the boundary between the two is left for the agent to guess.

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 an explicit precondition ('Confirm the recipients and exact wording with the user first, unless they gave both') and an explicit exclusion ('For person-to-person texts only: carriers filter bulk and marketing (A2P) traffic on personal numbers'), which steers bulk use toward the campaign siblings. It stops short of naming the alternative tool that should be used for bulk traffic.

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