Skip to main content
Glama

sms-verify

Estimate Cost

post_estimate_cost

What a verification SMS to this phone number would cost, in credits, and the number's country (region_code, ISO 3166-1 alpha-2; null when the number belongs to no assigned range). Nothing is sent. The price is for this number's carrier, so it can differ from the country's price in the price list. Group: Pricing. Billing per call: 0 Credits, Requests: metered (~0.71 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_estimate_cost"
  }
}

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.9/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 well: it discloses that no message is sent (no side effects), that billing is 0 credits per call but requests are metered, and that the quoted price is carrier-specific rather than country-level. It omits who can call it and what happens for invalid or unassigned numbers beyond the null region_code case.

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?

The return values and the no-side-effect guarantee are front-loaded in the first two sentences, followed by the pricing caveat. The trailing Group/billing/rate metadata is compact and genuinely useful rather than filler.

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 single-parameter lookup with no output schema, the description covers what is returned (credits, region_code) and reassures that no SMS is dispatched. It stops short of describing error or edge behavior (unroutable number, unsupported region) that an agent might need.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the target format is fully documented in the schema, so the baseline is 3. The description adds real meaning on top: the number determines both the country result and the carrier-specific price, and it explains the null region_code case, which is response semantics an agent would otherwise not anticipate.

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?

States a specific resource (the credit cost of a verification SMS to a given phone number) and the secondary return value (region_code in ISO 3166-1 alpha-2). 'Nothing is sent' implicitly distinguishes it from the actual send tool, though no sibling is named outright.

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?

'Nothing is sent' signals this is a dry-run/lookup rather than a send, which helps an agent pick it over post_send_numeric_verify. However, there is no explicit when-to-use statement, no mention of get_pricing as the country-level alternative, and no stated prerequisites or ordering (e.g., call before sending).

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