Skip to main content
Glama

X420 agent services

x420_validate_email-url-phone

Read-onlyIdempotent

Format validator (email, URL, phone): Syntax validation and normalisation: email (RFC 5322 simplified, lower-cased domain), URL (parsed, http/https), phone (E.164 normalisation with NANP rules). No network lookups. Not professional, legal, insurance, engineering, medical, financial or tax advice. Price: $0.01 USDC per call (x402 on Base). This hosted tool does NOT pay and does NOT return the deliverable: it validates the input and returns payment instructions (pay_to, network, price and the x402 URL to pay at). GET the url; read PAYMENT-REQUIRED from the 402; retry with PAYMENT-SIGNATURE (x402 v2). Or run the local x420-mcp server with your own wallet key to pay automatically. Deliverable once paid: JSON: email{valid, normalized, domain}, url{valid, normalized, host}, phone{valid, e164, country_code, national}.

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": "x420_validate_email-url-phone"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoURL to check (default: none)
emailNoemail address to check (default: none)
phoneNophone number to normalise (default: none)
default_countryNoISO 3166 alpha-2 for phones without a + prefix (default US)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior5/5

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

Annotations only declare it as a safe, idempotent, open-world read; the description goes well beyond that by disclosing the $0.01 USDC x402 cost, the fact that the hosted tool does NOT pay and does NOT return the deliverable, the exact 402/PAYMENT-SIGNATURE retry flow, and the alternative of running the local server with a wallet key. That is precisely the kind of operational context an agent cannot get from structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose is front-loaded and clear, but the body is dense and mixes four unrelated concerns: syntax rules, a legal disclaimer, a payment protocol walkthrough, and the paid output shape. The boilerplate 'Not professional, legal, insurance... advice' sentence and the duplicated title add length without helping the agent decide or invoke.

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?

No output schema exists, yet the description specifies the paid deliverable's JSON shape precisely (email{valid, normalized, domain}, url{valid, normalized, host}, phone{valid, e164, country_code, national}), and it explains the two-step payment handshake. The only real gap is what happens when zero parameters are supplied, for a tool with all-optional inputs.

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, but the description adds real semantic value the schema lacks: domain lower-casing for emails, E.164 normalisation with NANP rules for phones, and the http/https restriction for URLs. It also implicitly frames default_country as feeding the phone normalisation path.

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?

The opening clause names a specific verb and resource set: 'Format validator (email, URL, phone): Syntax validation and normalisation', and it enumerates the exact rules used for each (RFC 5322 simplified, parsed http/https URL, E.164 with NANP). The 'No network lookups' line implicitly separates it from network-flavoured siblings like x420_dns_lookup or x420_http_endpoint-check, though no sibling is named explicitly.

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?

It conveys the context (pure syntax checking, not live resolution) and gives detailed guidance on the payment workflow, but offers no explicit when-not-to-use guidance and never addresses the case where all four parameters are optional and nothing is supplied. The agent must infer that at least one of url/email/phone should be passed.

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