Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

Phone number validation: valid, E.164 format, country and line type

phone_validate
Read-only

Validate and format a phone number with the libphonenumber rules: whether it is valid and possible, the E.164 form, international and national formatting, country, calling code and line type (mobile, fixed-line, toll-free, VoIP…). Give +country code, or a national number and a two-letter country. Offline: nothing is sent and it does not say the line is in service. Use to clean contact lists or check a number before an SMS. Example: number=+1 650-253-0000. Price $0.01/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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_validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
numberYesPhone number, ideally with +country code
countryNoTwo-letter country for national numbers without +code (US, GB, SE…)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations it discloses the substantive behavioral facts: the lookup is offline ("nothing is sent"), it explicitly disclaims carrier/service-status information, it explains the cost model ($0.01/call, first 25 free, failed calls free) and clarifies why repeating a call costs money again — which usefully explains the idempotentHint=false annotation. That is real added context rather than restatement.

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 capability and its scope are front-loaded, and the closing sentence deliberately separates the safety profile ("Changes nothing") from the billing caveat. The pricing sentence is the longest and heaviest, but it carries information the agent cannot get from annotations, so it earns its space; the parenthetical field list is the only mildly wasteful redundancy.

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?

There is no output schema, and the description compensates by naming the return contents in the first sentence. Combined with the input-shape guidance, the offline disclaimer, and the cost model, an agent has everything needed to call it correctly and interpret the result without further documentation.

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 baseline is 3; the description goes slightly beyond by framing the two parameters as alternatives ("Give +country code, or a national number and a two-letter country") and supplying a concrete literal example (number=+1 650-253-0000). It does not add format/parsing edge cases beyond that, so it sits just above the baseline.

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?

The description opens with a specific verb+resource ("Validate and format a phone number") and then enumerates exactly what is produced: validity/possibility, E.164, international and national formats, country, calling code and line type. The parenthetical line-type list and the libphonenumber reference make it unmistakably distinct from the other validate_* siblings (IBAN, ISBN, Luhn, BIC).

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?

It states concrete use cases ("clean contact lists or check a number before an SMS") and gives input-shape guidance (give +country code, or a national number plus a two-letter country). It does not name an alternative tool or state when not to use it, but no sibling in the catalog overlaps in domain, so the routing ambiguity is low.

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.