RDAP API

Bulk Domain Lookup

bulk-domain-lookup

Read-only

Look up normalized RDAP registration data for several domain names in one pooled call. Requires a Pro or Business plan; every domain in the batch counts against the quota.

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": {
      "domains": "<domains>"
    },
    "name": "bulk-domain-lookup"
  }
}

Input Schema

Name	Required	Description
`whois`	No	Set false to refuse the WHOIS fallback for every domain in the batch, so a TLD with no RDAP server returns not_supported. Defaults to true.
`follow`	No	Follow the registrar RDAP link for richer data on thin registries such as .com and .net. Slower; defaults to false.
`domains`	Yes	The domain names to look up, e.g. ["example.com", "example.net"]. Between 1 and 10 per call. Unicode (IDN) names are accepted. Pass registered domains, not hosts such as "www.example.com".

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 16, 2026

changedInput schema / properties / domains / description

Previous value: -"The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted."New value: +"The domain names to look up, e.g. [\"example.com\", \"example.net\"]. Between 1 and 10 per call. Unicode (IDN) names are accepted. Pass registered domains, not hosts such as \"www.example.com\"."

First observedSep 6, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/openWorld/non-destructive, so the description's added value is the plan gating and the per-domain quota accounting — genuine behavioral facts not in structured data. It stops short of describing batch failure semantics (e.g. whether one bad domain fails the whole call), but covers the commercially important behavior well.

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?

Two sentences, zero filler, with the core action front-loaded and the plan/quota caveat second. Every clause earns its place.

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?

For a three-parameter read tool with no output schema, the description plus rich schema descriptions and annotations cover calling correctly. The notable remaining gap is return/error shape for partial batch failures, which 'normalized RDAP registration data' only hints at.

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 whois, follow, and domains are already fully documented in the schema, including the 1-10 limit and IDN handling. The description adds nothing parameter-specific, making the baseline 3 the correct score.

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 a specific verb and resource ('Look up normalized RDAP registration data') plus the batching scope ('several domain names in one pooled call'), which is exactly what separates it from the sibling domain-lookup. An agent can pick between single and bulk without opening either 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?

Gives real eligibility and cost context (requires Pro or Business plan; each domain counts against quota), which is useful pre-call guidance. However, it never states when to prefer this over domain-lookup for a single name, or when-not to batch, so alternative selection is left to inference.

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

All RDAP API tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?