Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Confirmed registrar price changes across the nine

ud_list_price_changes
Read-onlyIdempotent

Confirmed registrar price changes across the nine, newest first. Every input is optional.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: id, extension, registrar, registrarName, field, oldPrice, newPrice, currency, confirmedAt.

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/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 behavior, so the safety profile is fully covered. The description contributes the result ordering (newest first) and confirms no required inputs, but says nothing about result volume, bounds, or pagination for what is presumably an unbounded list.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences with zero filler, and the resource and ordering are front-loaded. Nothing could be cut without losing information, though the cryptic phrase 'the nine' does cost clarity rather than conciseness.

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?

The tool is low-complexity (one optional parameter) and has both rich annotations and an output schema, so description burdens are light. Still, the ambiguous scope phrase and the absence of any hint about result size bounds leave an agent slightly under-informed for a potentially large list.

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?

The single parameter has full schema description coverage enumerating the keepable keys, so the schema carries the semantics. The description's 'Every input is optional' adds only the optionality note, which the schema already encodes via an empty required list; no additional meaning about the fields filter is provided.

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 a specific resource (confirmed registrar price changes) and an ordering (newest first), which gives real substance. However, 'across the nine' is opaque — an agent cannot tell what scope that refers to — and nothing distinguishes this from close siblings such as ud_list_registrar_changes, ud_list_registrar_prices, or ud_list_price_traps.

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 tool versus the many similar list tools in the sibling set, and no exclusions or prerequisites. The only usage-adjacent note is that all inputs are optional, which describes calling convention rather than selection guidance.

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