Skip to main content
Glama

Lookproof DNS, mail and TLS security checks

RDAP domain lookup

rdap
Read-onlyIdempotent

Use when the user asks for a domain's whois or registration data: when it expires, the registrar, or if it is locked. Returns registrar, creation, change and expiry dates, statuses and name servers from RDAP. No contact data. Ex: 'When does example.com expire?'. Free trial without an API key: a few calls a day.

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

Input Schema

NameRequiredDescriptionDefault
domainYesA public domain name, e.g. example.com.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds genuinely new context: what fields come back, that contact data is excluded, and that unauthenticated use is throttled to a few calls a day. It does not describe failure behavior (domain not found, unsupported TLD, registry not offering RDAP), which keeps it short of a 5.

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?

Dense and front-loaded: trigger, return contents, limitation, example, and quota in five short sentences with no filler. The trailing 'Free trial without an API key: a few calls a day' is slightly cryptic in phrasing but earns its place as rate-limit information.

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?

For a one-parameter read tool with rich annotations, the description covers trigger, inputs, returned fields, and a key limitation. Because there is no output schema, enumerating the returned fields is exactly the compensating detail needed.

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 single parameter is fully described in the schema (maxLength 254, 'A public domain name, e.g. example.com'), so the schema does the heavy lifting. The description reinforces the intent via the example query but adds no format, normalization, or IDN/TLD constraints beyond what the schema states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (domain registration/whois data via RDAP) and the exact fields returned: registrar, creation, change and expiry dates, statuses, name servers. This implicitly separates it from resolution-oriented siblings like dns_lookup or nameservers, but no sibling is ever named, so the differentiation is left to inference.

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?

It gives an explicit trigger: 'Use when the user asks for a domain's whois or registration data: when it expires, the registrar, or if it is locked,' plus a concrete example query. There is a partial exclusion ('No contact data'), but no statement of when to prefer a sibling tool instead.

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.