Skip to main content
Glama

Web and geo tools (x402)

verify_domain

$0.002 via x402: Everything public about a domain in one call: A/AAAA, NS, MX, TXT, SPF record, DMARC policy, DKIM selectors found (google, default, selector1, selector2, k1, mail, dkim), DNSSEC flag, and RDAP registration data (registrar, created and expiry dates, status, nameservers). Pay 0.002 USDC through https://store.agentexchange.work/gw/verify/domain?name=example.com Via the Agent Exchange store gateway; s

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

Input Schema

NameRequiredDescriptionDefault
nameYesdomain name
x_paymentNoSigned x402 payment payload (optional; without it the answer is the price)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It does usefully disclose that the tool is metered ($0.002 via x402, paid in USDC through the store gateway) and the schema notes the unpaid-request behavior, but it says nothing about error handling, rate limits, or what happens on a malformed domain. Partial coverage for a no-annotation tool.

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 output enumeration is front-loaded and dense, which is good, but the price is stated twice ('$0.002 via x402' and 'Pay 0.002 USDC'), the payment URL is embedded mid-sentence, and the text is truncated mid-clause ('Via the Agent Exchange store gateway; s'), which hurts structure.

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 no output schema, the description must describe return values, and it does so comprehensively by enumerating every field group returned. It is docked for the truncated tail and the absence of any error/permission guidance, but for a 2-parameter read tool the return-value coverage is strong.

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 both parameters (name, x_payment) are already documented in the schema, and the description adds only an example URL (name=example.com). Baseline 3 applies when the schema does the heavy lifting and the description adds no syntax beyond it.

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?

States a specific verb+resource (verify a domain) and enumerates the exact payload returned (A/AAAA, NS, MX, TXT, SPF, DMARC, DKIM, DNSSEC, RDAP registration data), which is far more specific than a tautology. It does not explicitly contrast itself with the sibling verify_dns, so an agent must infer that this is the aggregate DNS+RDAP tool, keeping it short of a 5.

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 phrase 'Everything public about a domain in one call' implies the usage context (one-stop aggregate lookup) and the pricing line signals this is a paid call, but there is no explicit when-to-use vs when-not, and the sibling verify_dns is never named as the cheaper alternative. Usage is implied rather than stated.

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