Skip to main content
Glama

Sparetext

Send a text to each person

send_sms_batch
Destructive

Send a different text to each person in one batch, like each guest's own name and table, from the user's own number. Write each text in full; nothing is filled in for you. Up to 100 recipients in all. Confirm the list and the wording with the user first. Returns a batchId: check progress with get_batch. For people who expect the 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": {
      "messages": "<messages>"
    },
    "name": "send_sms_batch"
  }
}

Input Schema

NameRequiredDescriptionDefault
simNoOptional, Android only: which SIM sends them, numbered as on the phone.
send_atNoOptional: send later (ISO 8601, up to 30 days ahead).
messagesYesOne entry per text
device_idNoOptional: which phone sends them (see list_devices).
ttl_secondsNoOptional: drop any text not out this many seconds after it may go.

Output Schema

NameRequiredDescriptionDefault
noteNo
deviceYes
batchIdYes
messagesYes
estimatedCompletionAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedOutput schema / properties / estimatedCompletionAt
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare destructive, open-world, non-idempotent behavior; the description adds that texts come from the user's own number, that up to 100 recipients are allowed, and that the user should confirm before sending. It also explains carrier A2P filtering on personal numbers, which is meaningful behavioral context beyond the annotations. It doesn't cover failure handling or detailed auth needs, but the safety profile is well supported.

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 front-loaded with the core action and scope, then adds confirmation guidance, the get_batch follow-up, and the carrier caveat. Every sentence earns its place and there is no redundant restatement of the schema.

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

Completeness4/5

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

For a destructive batch send with an output schema, the description covers the important action, limits, confirmation requirement, and follow-up path via get_batch. It omits some edge-case behavior, such as what happens when only part of the batch fails, but the output schema and annotations fill in most of the remaining context.

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 coverage is 100%, so parameters like sim, send_at, device_id, and ttl_seconds are already documented. The description only reinforces the 100-recipient limit and the requirement to write each text in full; it adds little parameter-level meaning beyond 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?

The description states a specific verb and resource: send a different text to each person in one batch, from the user's own number. It clearly distinguishes the batch/personalized nature from a single-recipient sibling like send_sms, and gives concrete use-case framing (each guest's own name and table).

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?

It gives useful usage context: confirm the list and wording with the user first, and check progress with get_batch. It also warns about carrier filtering on personal numbers, which helps the agent decide whether this is appropriate. It does not explicitly contrast when to choose this over send_sms, but the batch scope is clear.

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