Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Ending's latest market figures

ud_get_tld_stats
Read-onlyIdempotent

The ending's latest market figures, and with history its last daily rows. 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. Changed2 schema fields changed
    • changedOutput schema / properties / data / properties / day / description
      Previous value: -"The rollup's day."New value: +"The day of these figures."
    • changedOutput schema / properties / data / properties / history / items / properties / day / description
      Previous value: -"The rollup's day."New value: +"The day of these figures."
  2. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds a little beyond that by explaining that supplying history changes the result to the last daily rows, but says nothing about data freshness, whether missing TLDs error or return empty, or result size.

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?

Two short sentences with the resource stated first and the required input second; nothing is padded. The second clause ('and with history its last daily rows') is grammatically awkward but not wasteful.

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 single-TLD read tool with full schema descriptions, complete annotations, and an output schema, the description covers enough to invoke it correctly. The remaining gap is routing versus sibling stats tools, which is a usage issue rather than a completeness 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 each parameter carries its own description, including format rules for tld. The description only restates that tld is required and the rest are optional, and its 'with history its last daily rows' phrasing adds a modest gloss on top of the schema's 'Days of daily rows, newest first'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names the resource ('the ending's latest market figures') and hints at a history option, but it is a noun phrase with no verb and relies on domain jargon ('ending') that the schema has to decode as a TLD. It does not distinguish this from siblings like ud_get_catalog_stats, ud_get_market_sales, or ud_get_trend, so an agent must guess which stats tool to pick.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use guidance and no named alternatives. 'Pass `tld` (such as ai); the other inputs are optional' is parameter mechanics, not selection guidance, so the agent gets no signal about when this tool is preferred over the market or trend siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Unique Domains toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources