Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Every recorded status or contention change of the round

ud_list_tld_application_changes
Read-onlyIdempotent

Every recorded status or contention change of the round, newest first. Every input is optional; limit sets the page size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ud_list_tld_application_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoWhat changed.
limitNoPage size, 20 at most.
sinceNoA day or an ISO 8601 timestamp: changes seen at or after it.
cursorNoThe `meta.cursor` of the previous page.
fieldsNoComma-separated top-level keys to keep: applicationId, string, kind, before, after, seenAt.

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, non-destructive, and closed-world behavior, so the safety profile is fully covered. The description adds useful behavioral detail: results are returned newest first and the set is paginated by page size. It does not explain cursor behavior or what happens when filters are combined, which would have pushed this higher.

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 core behavior front-loaded and no filler. The second sentence partially duplicates the schema's own parameter descriptions, which is the only waste.

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?

An output schema exists, so return values need no explanation, and the five optional filters are fully documented in the schema. What is missing is context an agent needs to choose this tool: what 'the round' refers to and how this listing differs from the near-identical ud_list_tld_changes sibling.

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 every parameter is already documented, including the enum for 'kind' and the meaning of 'since', 'cursor', and 'fields'. The description only restates optionality and that 'limit' is the page size, adding no meaning beyond the schema; 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 states a specific resource (recorded status or contention changes for a round's TLD applications) and its ordering (newest first), which is more than a restatement of the title. It stops short of distinguishing this from the very similar sibling ud_list_tld_changes, so an agent must infer the difference from the name alone.

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 mention of alternatives such as ud_list_tld_changes, ud_list_tld_phases, or ud_get_event, even though several siblings look like plausible substitutes. The only guidance given ('Every input is optional') is about invocation mechanics, not tool selection.

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