Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One TLD in full

ud_get_tld
Read-onlyIdempotent

Retrieve complete details for a single TLD—registry facts, launch phases, market trends, quality band, and registrar prices—to answer questions about one domain ending.

Instructions

One TLD in full: registry facts, phases, market, quality band and registrar prices. Use it when someone asks about one ending: who runs it, its launch phases, its market and its prices. Pass tld (such as ai).

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

Input Schema

NameRequiredDescriptionDefault
tldYesThe ending without the dot (`ai`), ASCII or `xn--` form; lowercased, a leading dot stripped.
fieldsNoComma-separated top-level keys to keep: slug, registry, phases, market, quality, registrars, githubRepoUrl.

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?

The annotations already declare readOnlyHint, idempotentHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds useful scope by listing the content that comes back, but it says nothing about data freshness, caching, or how the fields projection behaves. That is adequate, though not rich.

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?

The description is two sentences with the payload summary front-loaded and a use case following. The first sentence's enumeration and the second's use case slightly overlap, but nothing is wasted.

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 no explanation, and because the tool is single-resource and simple, the description covers enough of what is returned and when to call it. The only gap is routing the agent to sibling aggregate or price tools.

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%, and both parameters, including the comma-separated `fields` projection keys, are documented in the schema. The description only illustrates the `tld` format (such as ai) and adds no meaning beyond what the schema already provides, which makes the baseline of 3 appropriate.

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 the verb-plus-resource explicitly: one TLD in full, with the payload enumerated as registry facts, phases, market, quality band, and registrar prices. It doesn't distinguish itself against any specific sibling, so it falls just short of a 5.

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?

The description supplies a concrete trigger: use it when someone asks about one ending, who runs it, its launch phases, its market, or its prices. It gives no exclusions and names no alternatives, so an agent must infer that aggregate and price-list siblings exist.

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