Skip to main content
Glama

RDAP lookup

rdap_lookup

Registration data for a domain (IANA bootstrap, then the registry RDAP server), or an IP or ASN via rdap.org with RIPEstat as fallback. Returns registrar, dates, status, and nameservers or the network name, country, and holder. No contact emails or street addresses.

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

Input Schema

NameRequiredDescriptionDefault
ipNoIPv4 or IPv6 address.
asnNoASN, for example AS13335.
queryNoA domain, IP, or ASN when the kind is not given separately.
domainNoDomain name, for example example.com.

Output Schema

NameRequiredDescriptionDefault
okNo
kindNo
queryNo
statusNo
registrarNo
nameserversNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses the two-tier source chain including a fallback provider, and it explicitly scopes what is NOT returned ('No contact emails or street addresses'), which prevents wasted follow-up calls. It stops short of stating that this is a read-only operation, or mentioning rate limits and failure behavior when both sources fail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

Three sentences, each earning its place: what it covers and how, what comes back, and what is deliberately withheld. The scope statement is front-loaded and there is no filler.

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?

An output schema exists, so the description is not obligated to enumerate return fields, yet it summarizes them helpfully for quick triage. For a four-parameter, zero-required lookup with no annotations, the main remaining gap is input precedence between `query` and the kind-specific fields, plus error behavior when the fallback chain is exhausted.

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%, so all four parameters are already documented with examples in the schema, making 3 the baseline. The description's routing sentence implies that IP and ASN inputs take the rdap.org path rather than the bootstrap path, which adds a little meaning beyond the schema, but it never clarifies how `query` interacts with the specific `domain`/`ip`/`asn` fields or what happens if both are supplied.

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 a specific resource (registration data) and enumerates the supported resource kinds (domain, IP, ASN), plus the resolution chain used for each. 'Registration data' cleanly separates it from the sibling dns_lookup, which resolves records rather than registry ownership, so an agent can choose between them without opening a 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?

Useful routing detail is present: domains go through IANA bootstrap to the registry RDAP server, while IP/ASN go via rdap.org with RIPEstat as a fallback. But there is no explicit statement of when to prefer this tool over dns_lookup or other lookups, and no exclusion cases are named. The guidance 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