Skip to main content
Glama

apex-dev

Whois lookup

whois_lookup
Read-onlyIdempotent

WHOIS and authoritative IANA RDAP domain registration lookup (registrar, IANA ID, creation/update/expiry dates, age in days, DNSSEC, EPP statuses, nameservers). $0.001 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for terms, then call again with payment.

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

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain name to query (e.g. cloudflare.com).
paymentNosigned x402 payment payload (PAYMENT-SIGNATURE).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Annotations already declare read-only, idempotent, non-destructive, open-world, but the description adds the two behaviors annotations cannot express: a hard cost ($0.001 per call) with accepted payment rails (USDC on Arc/Base/Solana, XNT on X1) and the required two-call handshake before a paid result is produced. That is exactly the kind of pricing/auth context an agent needs and cannot infer 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.

Conciseness4/5

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

Front-loaded with purpose and return fields, then the paywall mechanics, with zero filler sentences. The long parenthetical of returned fields is dense but each item is informative, so nothing clearly warrants removal.

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, so enumerating the returned attributes in the description is necessary and is done well; the payment protocol and cost are also covered. Minor omissions remain — error behavior on an invalid or missing payment payload and any rate limits — but an agent has enough to call it correctly.

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 both parameters are already documented and the baseline is 3. The description earns a bump by explaining the otherwise opaque `payment` parameter operationally — it is omitted on the first call for terms and supplied on the second — which the schema's one-line 'signed x402 payment payload' does not convey.

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 and resource ('WHOIS and authoritative IANA RDAP domain registration lookup') and enumerates exactly what is returned (registrar, IANA ID, dates, age, DNSSEC, EPP statuses, nameservers). Sibling differentiation is only implicit — nothing explicitly distinguishes it from dns_records or tls_cert — but the registration-data field list effectively signals the difference.

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?

Gives concrete procedural guidance for the payment-gated flow: call once without `payment` to get terms, then call again with `payment`. That is actionable when-to-use guidance for a two-step protocol. It stops short of saying when to prefer this over alternatives like dns_records, so no exclusions or alternatives are named.

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