Skip to main content
Glama

Domain details

domain_details
Read-onlyIdempotent

Everything known about one domain: free or taken; for a taken one its registrar, when it was registered, when it expires and its nameservers; for a free one its price and buy_url, a link to register it at a registrar.

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

Input Schema

NameRequiredDescriptionDefault
domainYesOne domain name, such as brightfield.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds genuine behavioral value by spelling out the two outcome shapes (taken: registrar/dates/nameservers; free: price and buy_url), which is important for planning since there is no output schema. It does not mention rate limits, auth, or failure behavior for invalid domains.

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?

A single sentence, front-loaded with the core promise ('Everything known about one domain') and then branching cleanly on free vs taken. The semicolon chain is dense but every clause carries information; minor awkwardness keeps it from a 5.

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?

With no output schema, the description takes on the burden of describing returns and does so for both the taken and free cases, which is the key completeness need for a one-parameter lookup. Remaining gaps (error behavior, extra record fields such as status codes or contacts) are minor.

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% with a concrete example ('brightfield.com'), so the schema already carries parameter meaning. The description only reinforces that it takes a single domain, adding no format, TLD, or normalization guidance beyond what the schema provides; baseline 3 is appropriate.

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 resource (one domain) and enumerates exactly what is retrieved: availability status, and for taken domains the registrar, registration/expiry dates and nameservers. The phrase 'one domain' implicitly contrasts with bulk-oriented siblings like check_domains, but it never names an alternative, so it lands just short of a 5.

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 through the 'one domain' scoping and the free-vs-taken branching; there is no explicit 'use this when...' statement, no mention of when to prefer check_domains or search_name, and no stated prerequisites. An agent can infer it is the single-domain detail lookup, but must do the routing itself.

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