Skip to main content
Glama

Phone Number Format Check Payment Quote

phone_format_quote
Read-onlyIdempotent

Returns the payment terms for https://horizonpulse.dev/api/phone/format (base $0.002; USDC on Base only); this tool never runs the check or pays. Pay the 402 over HTTP with x402 v2: GET ?number=%2B14155552671 (or national digits with country=US; one number per call). Phone number format check for one number: valid or not for its numbering plan, region, country calling code, number type (mobile, fixed line, toll free...) and E.164, international, national and tel: URI forms. Offline numbering-plan data; does not show that a line is in service or who holds it, and is not a carrier lookup. A completed check is charged whether valid or not. Unparseable input: not charged. USDC on Base only.

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": "phone_format_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, the description discloses price ($0.002, USDC on Base only), billing edge cases ('a completed check is charged whether valid or not'; 'unparseable input: not charged'), and a crucial data caveat that it uses offline numbering-plan data and is neither a line-in-service check nor a carrier lookup. These are exactly the traits an agent needs before spending money.

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 clause front-loads what the tool returns and the payment rail, and every subsequent sentence carries distinct information (input format, capability scope, caveats, billing rules). It is dense semicolon-chained prose rather than bullets, which slightly slows scanning, but there is no filler.

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 zero-parameter quote endpoint with no output schema, the description covers everything needed: price and currency, payment protocol, exact request construction, what the purchased check answers, what it does not answer, and when billing applies. Nothing an agent must know before calling 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?

The schema is empty, so the description carries the full input burden and does so: it specifies the query-string shape, the 'number' value in E.164 with the '+' percent-encoded, the alternative national-digits form with 'country=US', and the one-number-per-call limit. Format details are adequate, though region/country value conventions beyond the US example are not covered.

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 names a specific verb and resource ('Returns the payment terms for https://horizonpulse.dev/api/phone/format') and immediately disambiguates from the underlying service ('this tool never runs the check or pays'). It also spells out what the priced check covers (validity, numbering plan, region, country calling code, number type, E.164/international/national/tel forms), so an agent can distinguish it from generic quote siblings at a glance.

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 the invocation path clearly: pay the 402 over HTTP with x402 v2 and issue a GET with '?number=...' (or national digits plus country=US), one number per call. It also gives a when-not boundary ('never runs the check or pays'), but it does not point to a sibling tool for actually executing the check, so the agent is left to infer the follow-up step.

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.