Skip to main content
Glama

Paid public-data feeds (x402, 0.002 USD)

Domain registration facts in one call from the registry RDAP service: registered or not, status, created, updated and ex

domain_rdap
Read-onlyIdempotent

Domain registration facts in one call from the registry RDAP service: registered or not, status, created, updated and expiry dates, registrar, nameservers, DNSSEC (domain=example.com). No registrant personal data. For brand, security and domain-investing agents. Pay per call $0.002 USDC on Base via x402.

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

Input Schema

NameRequiredDescriptionDefault
domainNodomain name, e.g. example.com
x_paymentNosigned x402 payment (X-PAYMENT header value); omit on the first call to receive the price and payment requirements

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive/openWorld, so the bar is lower, and the description still adds real behavior: no registrant personal data is returned, and the call is metered at $0.002 USDC on Base via x402. What is missing is what happens on a not-found or malformed domain and any rate-limit or retry behavior, which matters for an agent that has to handle payment failures.

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 return payload is front-loaded in a single dense sentence, followed by two short scoping and pricing sentences. Minor waste remains: the domain example duplicates the schema, and the title field repeats the description text.

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 enumerated field list effectively substitutes for one, and the pricing note tells the agent a payment step exists. For a simple two-parameter read lookup this is nearly complete; only error/not-found semantics are absent.

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 coverage is 100% and both parameters are already documented, including the x402 flow ('omit on the first call to receive the price and payment requirements'). The description adds little beyond that; the inline '(domain=example.com)' merely restates the schema example. Baseline 3 is appropriate when the schema carries the parameter burden.

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 states a concrete resource and source ('Domain registration facts ... from the registry RDAP service') and enumerates exactly what comes back: registered/not, status, created/updated/expiry dates, registrar, nameservers, DNSSEC. That field list makes it clearly distinguishable from domain-adjacent siblings like url_status or security_headers, which look at live HTTP behavior rather than registry records.

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 names intended audiences ('brand, security and domain-investing agents'), which implies usage but never states when to pick this over an alternative or when it is inappropriate. There is also no explicit note that the tool answers 'is this domain registered' even for unregistered names, though 'registered or not' hints at it.

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