Rdap

Domain

domain

Read-onlyIdempotent

Domain registration record from RDAP — registrar, registration/expiry dates, nameservers, status; a "domain not found" answer means the name is UNREGISTERED (available to register, subject to registrar checks). Keyless and authoritative (the registry's own service; the modern replacement for WHOIS). Covers gTLDs and ccTLDs including .io, .me, .de, .us, .ch, .sh and .ac, which IANA's bootstrap file omits. PREFER for "who is the registrar for ", "when does expire", "who owns ", "WHOIS for ", "is .com available/registered".

Input Schema

TableJSON Schema

Name	Required	Description
`base`	No	Optional registry RDAP base URL, e.g. "https://rdap.verisign.com/com/v1". Skips IANA bootstrap lookup — use it when a TLD comes back as tld_not_in_iana_bootstrap and you know the registry endpoint.
`name`	No	Domain name, e.g. "openai.com". Also accepted as `domain`.
`domain`	No	Alias for `name`.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

Changed2 schema fields changedAug 30, 2026

changedInput schema / examples

Previous value: -[
-  {
-    "name": "example.com"
-  },
-  {
-    "name": "google.org"
-  }
-]New value: +[
+  {
+    "name": "example.com"
+  },
+  {
+    "name": "google.org"
+  },
+  {
+    "domain": "pipeworx.io"
+  },
+  {
+    "base": "https://rdap.nic.ch",
+    "domain": "nic.ch"
+  }
+]

addedInput schema / properties / base

Added value: +{
+  "description": "Optional registry RDAP base URL, e.g. \"https://rdap.verisign.com/com/v1\". Skips IANA bootstrap lookup — use it when a TLD comes back as tld_not_in_iana_bootstrap and you know the registry endpoint.",
+  "type": "string"
+}

Changed1 schema field changedAug 13, 2026
- removedInput schema / required
```
Removed value: -[
-  "name"
-]
```

Changed2 schema fields changedJul 29, 2026

addedInput schema / properties / domain

Added value: +{
+  "description": "Alias for `name`.",
+  "type": "string"
+}

addedInput schema / properties / name / description

Added value: +"Domain name, e.g. \"openai.com\". Also accepted as `domain`."

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples

Added value: +[
+  {
+    "name": "example.com"
+  },
+  {
+    "name": "google.org"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "description": "RDAP domain registration record",
+  "type": "object"
+}

First observedMay 20, 2026

TDQS

A4.5/5.0

Behavior5/5

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

Annotations already signal read-only and open-world behavior, and the description adds meaningful detail: 'domain not found' means unregistered (available, subject to registrar checks), the service is keyless and authoritative, and it covers TLDs that IANA bootstrap omits. No contradiction with annotations.

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?

One dense paragraph packs definition, negative-result semantics, authority, coverage caveats, and usage triggers without filler. Every clause earns its place, and the emphasis on UNREGISTERED and PREFER is purposeful signal-boosting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Combined with the output schema and annotations, the description covers purpose, keyless access, authoritative source, TLD coverage gaps, open-world behavior, registry fallback via base, and natural-language triggers. Nothing needed for correct selection and invocation is missing.

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?

The input schema already describes all three parameters at 100% coverage: name, its alias domain, and base with endpoint guidance. The description adds no parameter-level semantics beyond what the schema provides, so the schema does the heavy lifting.

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?

States it returns a 'Domain registration record from RDAP' with registrar, registration/expiry dates, nameservers, and status, and explicitly identifies itself as the modern WHOIS replacement. The 'PREFER for' list names concrete queries like 'who is the registrar' and 'when does <domain> expire', distinguishing it from siblings such as nameserver, ip, and asn.

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?

Provides explicit conditions for use via 'PREFER for ...' and schema-level guidance for setting 'base' when a TLD is missing from IANA bootstrap. It does not name sibling alternatives or state when not to use it, so it stops short of the full 5 definition.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Rdap tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.