Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Latest stored registry record of one name

ud_get_name_registry
Read-onlyIdempotent

Retrieve a stored registry record for a domain name to check registration and expiry dates, registrar, status codes, nameservers, DNSSEC, and holder details.

Instructions

The latest stored registry record of one name: dates, registrar, status codes, nameservers, DNSSEC and holder. Use it when someone asks who holds a name, when it was registered or when it expires. A stored record, not a live lookup. Pass name (such as get.plumbing).

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

Input Schema

NameRequiredDescriptionDefault
nameYesA full domain name on an ending the catalog holds, lowercased, IDN as punycode. A bare word, a subdomain, an e-mail address or an unknown ending answers 400 `validation_failed` with `reason` and `suggestion`.
fieldsNoComma-separated top-level keys to keep: read, observedOn, observedAt, createdAt, updatedAt, expiresAt, registryUpdatedAt, registrar, eppStatuses, nameservers, dnssec, holder, transport.

Output Schema

NameRequiredDescriptionDefault
dataNo
metaNoThe day of the answer, and the page cursor of a list.
linksNoLinks of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

A4.2/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 closed-world, so the safety profile is covered. The description adds meaningful behavior the annotations cannot: this returns a stored snapshot rather than a live query, which tells the agent the data may be stale. It stops short of stating how stale 'latest' might be.

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?

Three short sentences, front-loaded with what the record contains, then the usage triggers, then the stored-vs-live caveat. No filler and nothing buried.

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?

An output schema exists, so return shape needn't be explained, and the two parameters are fully documented. The one residual gap for a 'latest stored' tool is the freshness/age of the snapshot, which an agent deciding between this and a live lookup would want.

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 schema already defines both `name` and the `fields` allow-list in detail. The description only adds an inline example ('such as get.plumbing'), which is minor beyond what the schema provides, 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?

States a specific verb+resource ('latest stored registry record of one name') and enumerates the record contents (dates, registrar, status codes, nameservers, DNSSEC, holder). The line 'A stored record, not a live lookup' sharply separates it from live-resolution siblings such as ud_get_name_dns.

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?

Gives three concrete trigger questions (who holds a name, when registered, when it expires), which is clear when-to-use guidance. It implies when-not-to-use via 'not a live lookup' but never names the live alternative explicitly, so routing to a sibling still requires inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools