Skip to main content
Glama

Phone Validation

phone-verify
Read-only

Check whether a phone number is valid and in service, its line type and carrier. Returns the status (valid when a carrier holds the number, invalid when it is malformed, outside its country's numbering plan, held by no carrier or not in service, unknown when its carrier data is withheld) with a sub-status, the number in international and national form, its country, line type (mobile, landline, fixed_voip, non_fixed_voip, toll_free and others), carrier, the network's line status and whether the handset is reachable now (null where the network does not say). A number its country's numbering plan rules out is answered free. Use before calling or texting a number you were given or found, or to sort a list of numbers into mobiles, landlines and VoIP. To find a person's number use phones. Pass number in international form (+ and its country code), or a national number with country. Cost: 3 credits, charged only when a call succeeds.

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": {
      "number": "<number>"
    },
    "name": "phone-verify"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesPhone number, in international form (+ and country code) or national with country.
countryNoISO 3166 two-letter country code of a national number.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/openWorld/non-destructive, and the description adds substantial context beyond them: the full status taxonomy and what each value means, sub-status, line status, handset reachability being null when unavailable, and the cost model ('3 credits, charged only when a call succeeds', free when numbering-plan rules rule a number out). The billing asymmetry is exactly the kind of behavioral detail structured fields cannot carry.

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?

Purpose and status semantics are front-loaded, then usage, then input format, then cost. It is dense but nearly every clause carries information; the parenthetical enumeration of line types is long but bounded and useful. Slightly overpacked as a single block, but not padded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only two-parameter lookup with no output schema, the description covers inputs, all returned fields, edge-case semantics (unknown status, null reachability, free invalid responses), cost, and alternative tools. Nothing an agent needs to call it correctly or interpret results is missing.

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 description coverage is 100%, so baseline is 3; the description goes further by stating the accepted input forms and their interaction — international form with '+' and country code, or a national number plus country. That clarifies why `country` is conditionally needed, which the schema alone only implies.

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?

Opens with a specific verb and resource: 'Check whether a phone number is valid and in service, its line type and carrier.' It then explicitly separates itself from the sibling that finds numbers ('To find a person's number use phones'), so an agent can route between the two without opening schemas.

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

Usage Guidelines5/5

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

Gives concrete when-to-use conditions ('before calling or texting a number you were given or found', 'sort a list of numbers into mobiles, landlines and VoIP') and names the alternative tool ('phones') for the adjacent task of finding a person's number. Both the trigger and the exclusion are stated.

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.