Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

send_bulk_sms

Sends the same SMS text to up to 500 recipients in one call. Batches over 50 are queued and return a jobId for progress tracking.

Instructions

Send the same SMS text to up to 500 recipients. Batches over 50 recipients are queued (HTTP 202) and return a jobId; use get_bulk_job to follow progress.

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

Input Schema

NameRequiredDescriptionDefault
toYesPhone numbers in international format.
fromNoApproved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
textYesCommon message text.
send_atNoSchedule for later: ISO 8601 with timezone, e.g. 2026-10-01T09:00:00+02:00 (max 30 days ahead). Omit to send now. Scheduled sends return a jobId that can be cancelled with cancel_scheduled.
idempotencyKeyNoOptional Idempotency-Key (e.g. a UUID). Repeating a call with the same key never sends the SMS twice; the original response is returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the most consequential behavior: an async threshold at 50 recipients, HTTP 202, and a returned jobId. Remaining gaps are permissions, cost implications, and what happens on partial delivery failures, none of which are mentioned.

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 tightly written sentences with the primary constraint front-loaded and the follow-up tool named last. Nothing is redundant and every clause carries information.

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 a five-parameter send tool with no annotations and no output schema, the definition covers the essentials: scope limit, async behavior, job handle, and follow-up tool. The remaining detail lives in a fully-documented schema, so an agent has what it needs to invoke this correctly.

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 all five parameters are already documented in the schema, including international format, sender ID defaults, scheduling, and idempotency. The description only reinforces that one text is shared across all recipients, adding little beyond the schema baseline.

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?

The description states a specific verb and resource ('Send the same SMS text') plus an explicit scope limit ('up to 500 recipients'), so the bulk nature of the operation is unmistakable. It stops short of naming send_sms as the single-recipient alternative, so differentiation relies on the agent knowing what the sibling does.

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 a clear usage condition (batches over 50 are queued) and routes the agent to get_bulk_job for progress tracking, which is actionable guidance. It does not state exclusions such as using send_sms for a single recipient or when to prefer scheduled sends, leaving some sibling selection to inference.

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