Skip to main content
Glama

sms-verify

Send Verify SMS

post_send_numeric_verify

Sends a six-digit verification code to a phone number by SMS and returns the code, so you can compare it with what the user types. The message reads 123-456 is your verification code. Don't share. The request is charged the message's cost in credits (cost), which depends on the destination country and carrier; a message that would cost more than 10,000 credits is not sent (max_cost_exceeded). Failed requests are not charged. Group: Verification. Billing per call: Credits: metered (~1021.01 avg).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "post_send_numeric_verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
bodyNoJSON request body.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / body / description
      Previous value: -"JSON request body. Example: {\"target\":\"+44 7459 034784\"}"New value: +"JSON request body."
    • addedInput schema / properties / body / properties
      Added value: +{
      +  "target": {
      +    "description": "The phone number in international format, with its country calling code, for example `+1 201 555 0123`. Spaces and dashes are allowed; a missing `+` is added.",
      +    "example": "+1 201 555 0123",
      +    "type": "string"
      +  }
      +}
    • addedInput schema / properties / body / required
      Added value: +[
      +  "target"
      +]
  2. First observed

TDQS

A3.7/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 discloses substantial behavior: the exact SMS template, credit charging, country/carrier-dependent cost, the 10,000-credit send threshold with max_cost_exceeded, and that failed requests are not charged. It could go further on retry/idempotency behavior, but the operational context is strong.

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?

The first sentence front-loads the action and return value, and most following sentences add useful billing or failure context. The final Group/Billing lines partially repeat the earlier cost discussion and add some administrative detail, but the description is still reasonably tight.

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 one-parameter tool with no output schema and no annotations, the description explains the return code, the template, cost behavior, and a key failure threshold. It is largely complete, though it could clarify the full response shape and whether retries incur additional charges.

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%, and the schema already explains the target phone number format, including international format and allowed spaces/dashes. The description adds only general context that it is a phone number receiving SMS, not additional parameter semantics.

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 gives a specific verb and resource: sends a six-digit verification code by SMS and returns the code for comparison with user input. It is clearly a verification-send operation, but it does not explicitly distinguish itself from the pricing siblings post_estimate_cost and get_pricing.

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 intended workflow is implied by “so you can compare it with what the user types,” which helps an agent understand when to use it. However, it gives no explicit alternatives, prerequisites, or guidance about using the pricing tools for preflight cost checks.

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