Skip to main content
Glama

Get domain details

get_domain
Read-only

Get detailed domain info including DNS records, nameservers, live registrar data, and subscription status. Auth codes are stripped.

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": {
      "id": "<id>"
    },
    "name": "get_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe domain ID

Schema Changelog

Changes observed during successful MCP inspections.

No schema history has been recorded yet.

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, so safety is covered. The description does add genuinely useful behavior beyond them: it discloses that registrar data is fetched live (implying a slower, external call) and that auth codes are redacted from the response. It still says nothing about failure modes, e.g. what happens for an unknown or unregistered ID.

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, front-loaded with the verb and resource, then the notable caveat. No filler or restatement of the title.

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 simple single-parameter read tool with no output schema, the description compensates well by enumerating the returned data and flagging the auth-code omission. The main remaining gap is error/not-found behavior and any latency expectation from the live registrar lookup.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With a single required parameter at 100% schema description coverage, the schema already carries the semantics (a 24-char hex domain ID). The description adds nothing about the ID, but there is nothing meaningful left to add, so the baseline applies.

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 uses a specific verb and resource ("Get detailed domain info") and enumerates the payload: DNS records, nameservers, live registrar data, subscription status. That is enough to distinguish it from a listing tool like list_domains, though no sibling is named explicitly.

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: this is the per-domain detail fetch keyed by ID. There is no explicit when-to-use/when-not statement, and the "auth codes are stripped" line gestures at get_authcode being the tool for that data without actually naming it as the alternative.

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.