Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Ending's latest market figures

ud_get_tld_stats
Read-onlyIdempotent

Retrieve the latest market figures and daily history for a domain ending (TLD) to track registrations, sales, prices, and trends over time.

Instructions

The ending's latest market figures, and with history its last daily rows. Use it when someone asks how one ending's market is doing, such as its registrations or sales over time. Pass tld (such as ai); the other inputs are optional.

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

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: tld, day, computedAt, tracked, available, availableOneWord, resell, expiring90d, registrations90d, medianBuy, medianRenew, cheapestRegistrar, sales12m, salesPrev12m, salesMedian12m, salesTrend, salesMonthly, sales30d, salesMedian30d, salesMedianPrev12m, panel, history.
historyNoDays of daily rows, newest first; absent = the latest row only.

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.8/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 safety behavior is covered. The description adds that history returns 'last daily rows' (newest-first cadence), which is a useful behavioral note beyond the annotations, but it says nothing about data freshness, caching, or cost of requesting 90 days.

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?

Three short sentences, front-loaded with what the tool returns followed by when to use it and how to call it. There is minor redundancy between 'latest market figures' and the title, but nothing wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Output schema exists and parameters are fully documented, so the description only needed to convey purpose and usage, which it does. An agent can call this correctly and interpret the result without further information.

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 description coverage is 100%, so all three parameters, their formats and the history 1-90 bound are already documented. The description only restates that tld is required and the others optional, plus an example value, which is standard baseline value rather than new meaning.

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 gives a concrete resource – one ending's latest market figures plus optional daily history rows – and thereby distinguishes itself from catalog- or market-wide siblings such as ud_get_catalog_stats or ud_get_market_sales. It falls short of 5 because 'ending' is domain jargon for TLD and no sibling is named as an explicit contrast.

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 sentence 'Use it when someone asks how one ending's market is doing, such as its registrations or sales over time' gives a clear triggering context with concrete example signals. It does not name any alternative or exclude overlapping cases (e.g. aggregate market queries), so it stops short of explicit when-not guidance.

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