Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One catalog name, by name or catalog id

ud_get_domain
Read-onlyIdempotent

Retrieve details for one catalog domain by its name or catalog ID, including status, price, registry, and ratings. Use it to look up a specific domain when you already know its name or ID.

Instructions

One catalog name, by name or catalog id. Use it when someone asks about one catalog name and holds its name or its catalog id. Pass nameOrId (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": {
      "nameOrId": "<nameOrId>"
    },
    "name": "ud_get_domain"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: id, name, ending, tracked, status, lifecycle, drop, ownableNow, price, registry, parking, length, format, shape, word, rating, verdict, value, comps.
nameOrIdYesA lowercase name or `dom_<uuid>`.

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

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured fields. The description adds no behavioral detail beyond that — no note on resolution precedence when the identifier is ambiguous, no caching or freshness behavior — so it neither helps nor contradicts.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is short and front-loaded, but the second sentence largely restates the first ("one catalog name" plus "name or catalog id" appears twice), spending words on repetition rather than new information. The only genuinely new content is the example identifier.

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 two-parameter read-only lookup with a full schema, complete annotations, and an output schema, the description covers the essentials. The remaining gap is that it says nothing about which sibling to prefer for adjacent name-related queries, but nothing required for correct invocation is missing.

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, including the accepted `dom_<uuid>` form. The description's only added value is a concrete example value (`get.plumbing`), which illustrates the name branch but does not explain the `fields` projection parameter at all.

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 states a specific verb and resource: fetch one catalog name, resolved either by name or by catalog id. The singular scope ("One catalog name") distinguishes it from list-style siblings, but no sibling is named, so the boundary with closely-related single-name lookups is left implicit.

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 condition: invoke when someone asks about one catalog name and already holds its name or its catalog id. There are no when-not conditions or named alternatives, but the triggering context is clear enough for an agent to act on.

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