Skip to main content
Glama

phone_parse

Parse and validate up to 50 phone numbers to E.164, returning validity, country, calling code, type, and national/international formats.

Instructions

Phone number parsing and validation to E.164 (libphonenumber numbering plans): validity, country, calling code, type (mobile, fixed line, toll-free…), national/international formats, tel: URI. Up to 50 numbers. No carrier lookup, no call. Costs 0.001 USDC on Base per successful call (x402). Without a payment key this tool returns the 402 challenge.

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

Input Schema

NameRequiredDescriptionDefault
phoneYesNumber(s); separate with ; or newline
countryNoDefault ISO country for national numbers

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.7/5.0
Behavior5/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 so well: it discloses per-call pricing (0.001 USDC on Base), the x402 payment scheme, and the exact failure mode without a key (a 402 challenge rather than an error or silent failure). A batch limit is also stated, which is the kind of operational constraint an agent needs before invoking.

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?

Dense but front-loaded: purpose first, then output fields, then limits, then cost/auth. Every clause carries information an agent would otherwise have to discover by trial, and there is no marketing filler or repetition of the schema.

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?

No output schema exists, and the description compensates by listing the returned fields. Cost, payment precondition, batch limit, and exclusions are all covered, leaving nothing material an agent needs before calling correctly.

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%, so the schema already documents 'phone' (multiple, ; or newline separated) and 'country' (ISO default). The description still adds value by capping the batch at 50 numbers and by tying country to libphonenumber numbering-plan resolution, which explains why the default-country parameter matters for national-format input.

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 (parse/validate) and resource (phone numbers) with an explicit target format (E.164 via libphonenumber numbering plans), then enumerates the outputs produced: validity, country, calling code, type, formats, tel: URI. No sibling tool in the list does phone-number work, and the description forecloses confusion with carrier-lookup or call tools.

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?

Clear context for use plus concrete boundaries: batch cap of 50 numbers, and explicit exclusions ('No carrier lookup, no call') that stop an agent from over-expecting. It also states the payment prerequisite. It does not name an alternative sibling for adjacent needs (e.g., email_check), so it falls short of a 5.

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