Skip to main content
Glama

DomainVet

Domain registration age, expiry and registrar (RDAP)

rdap_domain
Read-onlyIdempotent

Look up a domain's registration record via RDAP (the modern WHOIS): registration date, age in days/years, expiry date and days left, registrar, status flags, nameservers and DNSSEC. A domain registered days ago is a strong phishing/scam signal.

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_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesDomain name

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and open-world, so safety is covered; the description goes beyond them by naming the data source (RDAP, described as the modern WHOIS) and itemizing every returned field, which matters because no output schema exists. It omits operational traits such as rate limits, behavior for unregistered domains, and RDAP coverage gaps across TLDs.

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 and returned fields front-loaded and the interpretive payoff placed last. Nothing repeats the name or annotations.

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 one-parameter lookup with no output schema, the description is nearly sufficient: it explains the source and the return payload, which the schema cannot. The remaining gap is failure semantics — what happens for an unregistered domain or a TLD without RDAP service — which an agent would want before calling.

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?

There is a single required 'domain' parameter with full schema description coverage, so the schema already carries the meaning. The description adds nothing about format constraints (bare name vs. URL vs. subdomain) or internationalized domains, so it neither compensates nor detracts.

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 gives a specific verb and resource ('Look up a domain's registration record via RDAP') and enumerates what comes back: registration date, age, expiry, registrar, status flags, nameservers, DNSSEC. It is clearly a registration-data tool rather than a resolver, though the mention of nameservers and DNSSEC creates mild surface overlap with the dns_lookup sibling that is never explicitly disambiguated.

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?

Usage is only implied: the closing sentence frames the tool as a phishing/scam signal via domain age, which hints at a reputation-assessment context. There is no explicit statement of when to reach for this instead of dns_lookup or ssl_certs, and no exclusions or prerequisites are given.

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