Skip to main content
Glama

Look up domain

lookup_domain
Read-onlyIdempotent

Use this when the user wants a whois lookup or a domain lookup: which registrar holds this domain, the domain expiration date, when does my domain expire, a domain registrar lookup, the domain age, the nameservers, or to check domain expiry for up to 20 domains at once. Reads live RDAP registry data and returns the registrar, the creation, expiry and last-update dates, the days left before expiry, the status codes with a plain explanation, the nameservers, DNSSEC and the registrar abuse contact, plus a CSV of the batch sorted by expiry date. Only TLDs that publish an RDAP service are covered; personal data is usually redacted by registries and a not-found result does not mean the domain can be bought. Do not use for IP address lookups, DNS record resolution, website uptime or SSL certificate checks.

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

Input Schema

NameRequiredDescriptionDefault
domainsYesOne to 20 domains or URLs, e.g. example.com. Separate bare domains with commas or semicolons. Separate URLs with spaces or new lines to preserve URL punctuation. IDNs are accepted.

Output Schema

NameRequiredDescriptionDefault
countYes
shownYes
resultsYes
downloadsYes
retrievedYes
truncatedYes
registeredYes
source_urlYes
source_nameYes
unsupportedYes
not_registeredYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domains / description
      Previous value: -"One to 20 domains (up to 253 characters each) or URLs (up to 2,048 characters each), e.g. example.com, zovo.one. Separate bare domains with commas or semicolons; use new lines or spaces between URLs with paths or queries so their punctuation stays inside the URL. IDN names are accepted."New value: +"One to 20 domains or URLs, e.g. example.com. Separate bare domains with commas or semicolons. Separate URLs with spaces or new lines to preserve URL punctuation. IDNs are accepted."
  2. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the description's job is to add operational caveats — and it does: live RDAP registry data, TLD coverage limited to registries publishing RDAP, personal data usually redacted, and that a not-found result does not mean the domain is available. It also notes the 20-domain batch ceiling and the sorted CSV output, none of which appears in the annotations.

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?

It is front-loaded with the trigger and ends with the exclusions, which is the right ordering. However, the mid-sentence paraphrase chain ('which registrar holds this domain, the domain expiration date, when does my domain expire, a domain registrar lookup, the domain age') is repetitive keyword padding that could be tightened without losing retrieval value.

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?

An output schema exists and annotations cover the safety profile, so the description only needs trigger, scope and caveats — all present, including coverage limits and redaction semantics. Nothing an agent needs in order to call this correctly with one string of domains 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?

Schema description coverage is 100% and the single parameter already documents comma/semicolon vs. space/newline delimiters and IDN support. The description only restates the batch ceiling ('up to 20 domains at once') without adding format or edge-case detail beyond the schema, so the 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?

The description opens with a concrete verb+resource pair ('whois lookup or a domain lookup') and then enumerates the exact data returned: registrar, expiration date, domain age, nameservers, expiry. An agent can distinguish this from DNS/IP/SSL tools without opening the schema, and it needs no sibling differentiation since none exist.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives an explicit trigger ('Use this when the user wants...') keyed to natural user phrasings, then an explicit exclusion list: 'Do not use for IP address lookups, DNS record resolution, website uptime or SSL certificate checks.' Both the positive and negative boundaries are stated, which is the strongest form of routing guidance.

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