Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Latest stored DNS reading of one name

ud_get_name_dns
Read-onlyIdempotent

Retrieve the latest stored DNS reading for a domain name and its parking venue to check whether it points anywhere or is parked, and identify the parking service.

Instructions

The latest stored DNS reading of one name, with its parking venue. Use it when someone asks whether a name points anywhere or is parked, and with which parking service. 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_dns"
  }
}

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, ns, a, aaaa, cname, mx, hasWebsite, parking.

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/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 behavior, so the bar is lower. The description still adds a real behavioral nuance by specifying the reading is 'latest stored' rather than a live DNS lookup, which tells the agent results may lag; it omits freshness window and error behavior beyond what the schema states.

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, zero waste, with the identifying scope front-loaded before the usage guidance. Nothing is repeated from the title or schema.

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 values need not be described, and the input schema is fully annotated. What remains is the stored-versus-live caveat, which is present but thin; a freshness note would make it complete for a data-reading tool.

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 the schema already documents both `name` and `fields` thoroughly. The description adds only a format example ('get.plumbing') for `name` and says nothing new about `fields`, so it meets the baseline without exceeding it.

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 names a specific resource and qualifier: 'the latest stored DNS reading of one name, with its parking venue.' The word 'stored' usefully distinguishes it from any live-lookup sibling, though it does not explicitly contrast with adjacent name tools like ud_get_name or ud_get_domain.

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?

It gives an explicit use case: 'when someone asks whether a name points anywhere or is parked, and with which parking service.' That is a clear trigger, but there are no when-not conditions or named alternatives for adjacent queries such as registry or auction data.

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