Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Latest stored registry record of one name

ud_get_name_registry
Read-onlyIdempotent

The latest stored registry record of one name: dates, registrar, status codes, nameservers, DNSSEC and holder. 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 observed

TDQS

A3.5/5.0
Behavior3/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 safety is covered. The word 'stored' adds a genuinely useful nuance — this reads a cached registry snapshot rather than performing a live lookup — but the description says nothing about how fresh that snapshot is or what comes back when no record exists.

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?

Two tight sentences, front-loaded with the resource definition followed by the call instruction. The field list is partly redundant with the output schema, but it is short enough not to feel wasteful.

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 an output schema, full parameter descriptions, and rich annotations, the description only needs to fix what the resource is and how to call it, which it does. Missing only staleness/empty-result semantics that an agent might 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?

Schema coverage is 100%, so both parameters are already documented in structured form, including the 400 validation_failed behavior. The description contributes only an example value ('get.plumbing') and ignores the `fields` projection parameter entirely, so it sits at the baseline.

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?

Names a specific resource ('registry record of one name') and enumerates the payload it exposes (dates, registrar, status codes, nameservers, DNSSEC, holder), which is far more than a restatement of the title. It does not differentiate itself from near-siblings such as ud_get_name or ud_get_name_dns, but the record-vs-lookup distinction is at least implied by 'stored'.

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 implied only: 'Pass `name`' with an example. There is no statement of when to prefer this over ud_get_name, ud_get_name_dns, or ud_get_domain, and no exclusion or prerequisite is given.

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

All Unique Domains toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources