Skip to main content
Glama

domain_rdap_domain

Read-only

Fetch one domain registration record from the authoritative RDAP registry selected through IANA bootstrap data. Contact details may be redacted; only registry-provided fields are returned.

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

Input Schema

NameRequiredDescriptionDefault
domainYesBare registrable domain such as github.com; required.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

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?

The annotations already declare read-only, open-world access, so the description's value is the added caveat that contact details may be redacted and only registry-provided fields come back. That manages expectations on completeness, which the annotations cannot convey.

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 short sentences with the action front-loaded and the caveat second. Nothing is redundant or padded.

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 return structure need not be described, and redaction behavior plus registry-selection logic is covered. It stops short of mentioning failure modes such as unregistered or non-RDAP TLDs, which would matter for a bootstrap-based lookup.

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 the single 'domain' parameter is already documented with an example. The description restates the resource but adds no format rules beyond the schema, so baseline 3 applies.

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 ('Fetch one domain registration record') plus a distinguishing mechanism (RDAP registry chosen via IANA bootstrap), which separates it from the sibling domain_rdap_ip and DNS lookups like domain_dns_resolve.

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?

The implicit use case — get registration data for a single domain — is clear, but there is no explicit when-to-use versus when-not guidance and no sibling alternative is named. An agent must infer that DNS resolution or IP RDAP belongs to other tools.

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.