Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

send_sms

Send an SMS through the TopSMS gateway to a phone number; supports optional sender ID, scheduled delivery, and returns message ID, segment count, and price.

Instructions

Send one SMS message via the TopSMS SMS gateway (topsms.eu / topsms.cz). Costs credit: 160 GSM-7 chars = 1 SMS, 70 with other diacritics/emoji. Returns message id, number of segments and price in your account currency (field currency: EUR for topsms.eu accounts, CZK for topsms.cz).

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_sms"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPhone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted).
fromNoApproved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
textYesMessage 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

A3.7/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden. It discloses real behavioral facts beyond structure: it consumes credits, segment counting rules (160 GSM-7 chars vs 70 with diacritics/emoji), and exact return fields including currency semantics per domain. However it says nothing about failure modes such as insufficient credit, invalid sender ID rejection, or authentication requirements, which matter for a metered write operation.

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?

Three tight sentences, front-loaded with the action and provider before cost and return details. The parenthetical currency explanation is slightly dense but every clause carries operational meaning; no filler sentences.

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?

With no output schema, the description correctly compensates by naming the return payload (message id, segment count, price, currency field). Cost model and provider-specific currency are covered. The remaining gap is error/edge-case behavior on a credit-consuming send, which the description leaves unaddressed.

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 the baseline is 3. The description does add genuine meaning for the 'text' parameter by explaining how character count maps to billable segments (160 GSM-7 vs 70 with diacritics/emoji), which the schema's maxLength of 1600 does not convey, but it says nothing extra about 'to', 'from', 'send_at', or 'idempotencyKey'.

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 ('Send one SMS message') and pins the provider ('TopSMS SMS gateway (topsms.eu / topsms.cz)'). The word 'one' implicitly separates it from the send_bulk_sms sibling, so an agent can route singles vs bulk without opening either schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'one SMS message' vs the bulk sibling is the only routing signal. It never names an alternative or a condition (e.g. 'for multiple recipients use send_bulk_sms', or when to prefer verify_send). Adequate but the agent must infer the boundary.

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