Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Every dated launch phase of the ending, chronological

ud_list_tld_phases
Read-onlyIdempotent

Every dated launch phase of the ending, chronological. Pass tld (such as ai).

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

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: id, phase, startsOn, endsOn, programLabel.

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, so the safety profile is fully covered. The description's one genuine addition is that results come back in chronological order. It says nothing about empty-result behavior for TLDs without launch phases, unknown-TLD errors, or result size limits.

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 scope and ordering front-loaded and zero filler. The first sentence is a noun fragment rather than a verb phrase, which makes it marginally less scannable than it could be.

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?

An output schema exists, so return shape need not be explained, and with one required scalar parameter plus full annotation coverage the call mechanics are clear. The remaining gap is selection rationale against the many sibling TLD tools, which is left entirely implicit.

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%: the `tld` property already explains dot-stripping, lowercasing, and the ASCII/`xn--` forms, and `fields` enumerates the selectable keys. The description's '(such as ai)' duplicates the schema example rather than adding normalization or edge-case detail, so 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 specific resource (every dated launch phase) scoped to a single TLD and states the ordering (chronological), which is concrete enough to distinguish it from the stats/lookup siblings. It stops short of naming a contrast case such as ud_get_tld, and the word 'ending' is house jargon for TLD that only the schema disambiguates.

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?

The only guidance is 'Pass `tld` (such as ai)', which restates the required parameter rather than saying when to choose this tool. Nothing tells the agent how this differs from ud_get_tld or ud_list_tld_changes, nor what happens if the TLD has no recorded phases.

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