Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

verify_send

Send a one-time SMS verification code for login, registration, or payment confirmation. Generates and stores the OTP, then returns a verification ID.

Instructions

Send a one-time verification code (OTP) by SMS for login, registration or payment confirmation. TopSMS generates and stores the code; returns a verification id. Limits: 5 codes per number per hour, 30 s between codes.

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": "verify_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYesPhone number in international format, e.g. +420601234567 (Czech numbers without prefix are accepted).
ttlNoValidity in seconds, 60-1800 (default 300).
fromNoApproved Sender ID (max 11 chars). Omit to use the default sender "TopSMS".
brandNoYour app or company name shown in the SMS ("MyShop: your verification code is ...").
lengthNoCode length 4-8 digits (default 6).
localeNoSMS language (default cs).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations supplied, the description does real work: it discloses that the code is generated and stored server-side, that a verification id is returned, and it states explicit throttling rules (5 codes per number per hour, 30 s between codes). It stops short of explaining cost, error conditions, or any auth/permission requirements, which is the main remaining gap for an unannotated mutation tool.

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 short sentences, front-loaded with the action and use case, followed by the side effect/return value and then the limits. Nothing is redundant and every sentence adds information.

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 6-parameter tool with no output schema, the definition supplies the return value (a verification id) and the operational limits, which is what an agent most needs before calling. Only the absence of any mention of authentication, cost, or failure behavior keeps it from being fully complete.

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%, with per-field descriptions covering format, ranges, defaults and the locale enum, so the schema carries the parameter burden. The description adds no field-level meaning beyond that and only implies the ttl/limits relationship via the rate-limit sentence; baseline 3 applies.

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 a one-time verification code (OTP) by SMS') plus the concrete use cases, and goes on to distinguish the behavior from a plain SMS send by noting TopSMS generates and stores the code and returns a verification id. An agent can tell this apart from send_sms and see it pairs with verify_check without opening any schema.

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?

The phrase 'for login, registration or payment confirmation' gives clear contextual guidance on when to reach for this tool. However, it never names an alternative or a when-not condition — an agent must infer on its own that verify_check is the follow-up and that send_sms is for non-OTP messaging.

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