Skip to main content
Glama
TopSMS MCP server

TopSMS MCP server

verify_check

Checks a user-entered verification code against an SMS OTP request, returning validity, status, and remaining attempts so you can confirm or reject the code.

Instructions

Check a verification code the user entered. Returns valid true/false, status (approved, pending, expired, failed, canceled) and attempts left (max 5 attempts per code).

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": {
      "code": "<code>"
    },
    "name": "verify_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoVerification id returned by verify_send (preferred).
toNoAlternatively the phone number; checks the latest code sent to it.
codeYesCode entered by the user.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.2

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the return shape (valid boolean), the full status enum (approved, pending, expired, failed, canceled), and the attempt limit of 5 per code, which is a real throttling constraint. It stops short of saying whether a successful check consumes the code or what happens on an invalid id/to, so it is not exhaustive.

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 sentences, front-loaded with the action and followed by the return contract. Every clause earns its place — nothing is repeated from the name and nothing extraneous is included.

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?

There is no output schema, so the description's return-value summary is doing necessary work and covers the key states and the attempt budget. It is nearly complete for a 3-parameter tool; only edge behavior (invalid code, exhausted attempts, whether the code survives a successful check) is left implicit.

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 id, to, and code are already documented in the schema, including the id-preferred / phone-number-fallback relationship. The description adds no parameter-level meaning beyond that, so the baseline of 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 — 'Check a verification code the user entered' — which is immediately distinguishable from the sibling verify_send (sending vs. checking). An agent knows exactly what operation this performs without opening the 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?

The phrase 'the user entered' implies the natural usage point (after the user supplies a code), but there is no explicit when-to-use versus alternatives, no statement about calling it before/after verify_send, and no guidance on what to do once attempts are exhausted.

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