Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Ending's public registry changes, newest first

ud_list_tld_changes
Read-onlyIdempotent

The ending's public registry changes, newest first. 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_list_tld_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesThe ending without the dot (`ai`), ASCII or `xn--` form; lowercased, a leading dot stripped.
limitNoPage size, 20 at most.
cursorNoThe `meta.cursor` of the previous page.
fieldsNoComma-separated top-level keys to keep: kind, after, seenOn.

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 observed

TDQS

B3.2/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 is covered. The description's one genuine addition is the ordering guarantee ('newest first'), which affects how an agent interprets results; it says nothing further about pagination behavior or freshness beyond what the schema and output schema convey.

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 and ordering front-loaded and no filler. The second sentence largely duplicates schema information, which is minor waste but not confusing.

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

Completeness3/5

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

For a read-only paginated list with a fully documented schema and an output schema, the essentials are present, so return values need not be explained. However, an agent choosing among ~50 sibling tools gets no routing signal, which is the main missing piece.

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%, with `tld` format, `limit` bounds, `cursor` provenance and `fields` projection all documented in the schema. The description only restates that `tld` is required and the others optional, adding no new semantics, so the baseline 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 names a concrete resource (the ending's public registry changes) and a verb (list, newest first), plus the required `tld` argument, so an agent knows what it retrieves. It does not distinguish this from related siblings such as ud_list_registrar_changes or ud_get_tld, and the word 'ending' is domain jargon rather than the more familiar 'TLD'.

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 statement of when to use this versus the many sibling list/get tools, nor any exclusion or prerequisite. The only guidance is the mechanical note that `tld` is required and the rest optional, which is already evident from the schema.

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