Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Every registrar's list price for one ending

ud_list_tld_prices
Read-onlyIdempotent

Compare registrar list prices for a single TLD to pinpoint low-cost registration or renewal options and flag renewal traps.

Instructions

Every registrar's list price for one ending, with the cheapest and trap marks. Use it when someone asks where one ending is cheapest to register or to renew. Pass tld (such as io).

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_list_tld_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesThe ending without the dot (`ai`); lowercased, a leading dot stripped.
fieldsNoComma-separated top-level keys to keep: registrar, name, homepageUrl, purchasePrice, renewalPrice, transferPrice, currency, isPromo, regularPurchasePrice, renewalTrap, cheapest, cheapestRenewal, cheapestTransfer.

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 cover the safety profile (read-only, idempotent, non-destructive, closed-world), so the bar is low. The description still adds substantive behavior beyond them by disclosing that results carry cheapest markers and renewal-trap flags, which affects how the agent should interpret and present results.

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: what it returns, when to call it, and the key parameter. Scope and the actionable trigger are front-loaded, and no sentence is filler.

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 only two parameters, full schema coverage, an output schema, and complete annotations, the description supplies everything needed to select and call the tool correctly. Minor omission: it does not clarify that the `tld` must be a live ending or what happens for an unknown one.

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 the schema already documents both `tld` (dot-stripped, lowercased, with an example) and the `fields` projection keys. The description's "Pass `tld` (such as io)" restates what the schema says rather than adding new meaning, so the baseline of 3 applies.

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 resource and scope: registrar prices for a single TLD, plus cheapest and renewal-trap flags. It is clearly distinct from a per-registrar listing, but it never names the closest sibling (ud_list_price_traps) explicitly, so the differentiation is implied rather than stated.

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?

"Use it when someone asks where one ending is cheapest to register or to renew" gives a concrete triggering question. There is no when-not guidance or named alternative for related lookups (e.g. price changes or registrar-wide views), leaving that inference to the agent.

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