Skip to main content
Glama

Antigravity x402 & MCP Gateway

recon_rdap_domain

[0.004000 USDC via x402] Queries authoritative IANA RDAP registries for any public domain to extract registrar identity, registration and expiration timestamps, EPP status flags, DNSSEC delegation status, and nameservers.

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

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain name to query via IANA RDAP (e.g., 'cloudflare.com').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.004000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

No annotations exist, so the description carries the full burden: it discloses the cost (0.004000 USDC via x402), the upstream source (authoritative IANA RDAP), and the read-only nature of a lookup. It does not disclose failure behavior for nonexistent/reserved domains, rate limits, or latency, which are relevant for a network-dependent paid call.

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?

A single sentence with the price/cost marker front-loaded and no filler. Minor quibble: the bracketed USDC pricing partially duplicates the cost information already in the payment signature parameter description.

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?

There is no output schema, but the description compensates by enumerating the returned fields, so an agent knows what it will receive. For a two-parameter read-only lookup the coverage is nearly complete; only edge-case behavior (invalid domain, payment rejection) is unaddressed.

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 'domain' and 'x402_payment_signature' are already documented in the schema, including the example and accepted chains. The description adds no syntax, validation, or format detail beyond that, so the baseline 3 applies.

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 description gives a specific verb and resource ('Queries authoritative IANA RDAP registries for any public domain') and enumerates exactly what is extracted: registrar identity, registration/expiration timestamps, EPP status flags, DNSSEC delegation status, and nameservers. That field list makes it clearly a raw registry-lookup tool rather than the sibling audit_domain_security_posture, though it never names that alternative 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?

'For any public domain' implies a usage context, and the price prefix signals this is a paid call. However, there is no explicit when-to-use/when-not guidance and no mention of a sibling for higher-level security scoring. The payment flow nuance (omit signature to get a quote) lives only in the schema, not the description.

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.