Skip to main content
Glama

x420_validate_email-url-phone

Validates and normalizes email addresses, URLs, and phone numbers offline without network lookups, returning corrected values, domain or host details, and E.164 phone formatting.

Instructions

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. PAID: $0.01 USDC per call, settled on Base via x402 from the wallet in X420_MCP_WALLET_PRIVATE_KEY (real money). Returns: JSON: email{valid, normalized, domain}, url{valid, normalized, host}, phone{valid, e164, country_code, national} - the deliverable plus X420's signed receipt and the settlement transaction. Example input: {"email":"Owner@Example.COM","phone":"(817) 555-0142"}.

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 observedv1.0.2

TDQS

A4.1/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false, openWorldHint=true and not idempotent; the description goes far beyond them by disclosing that each call costs real money ($0.01 USDC settled on Base via x402 from X420_MCP_WALLET_PRIVATE_KEY), that no network lookups occur, and that the response includes a signed receipt and settlement transaction. That payment/auth context is exactly the behavioral information an agent cannot get from structured fields, and it does not contradict the annotations (the call moves funds despite destructiveHint=false, which is explained).

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 definition is front-loaded with purpose, then domain rules, pricing, return shape, and an example — a sensible order with no repeated content. The only overhead is the full legal disclaimer sentence, which is boilerplate but arguably necessary for a paid financial-adjacent tool.

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?

With four optional parameters and no output schema, the description correctly spells out the returned JSON shape (email{valid, normalized, domain}, url{...}, phone{...}) plus receipt and settlement artefacts, which is what an agent needs. It stops short of describing failure modes (e.g. invalid input, insufficient wallet balance) and the all-optional parameter pitfall, leaving minor gaps for a paid tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all four fields including default_country's ISO 3166 alpha-2 / default US behaviour. The description adds the NANP framing and a concrete example input showing email plus phone, but it never states that all parameters are optional and that at least one target field must be supplied for the call to be meaningful. Baseline 3 is appropriate given the schema does the heavy lifting.

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 the specific resource (email, URL, phone), the operation (syntax validation and normalisation), and the exact standards applied (RFC 5322 simplified, http/https parsing, E.164 with NANP rules). The phrase 'No network lookups' cleanly separates it from network-probing siblings such as x420_dns_lookup, x420_http_endpoint-check and x420_tls_certificate, so an agent can route correctly without opening the schema.

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?

The sentence 'No network lookups' implicitly tells the agent to pick this tool for offline syntax checks rather than reachability checks, and the example input demonstrates a multi-field call. However, there is no explicit when-to-use / when-not-to-use statement and no named alternative, so the routing guidance is inferential rather than stated.

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