Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

A registrar's confirmed list-price changes, newest first

ud_list_registrar_changes
Read-onlyIdempotent

A registrar's confirmed list-price changes, newest first. Pass registrar (such as namecheap).

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": {
      "registrar": "<registrar>"
    },
    "name": "ud_list_registrar_changes"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: id, extension, registrar, registrarName, field, oldPrice, newPrice, currency, confirmedAt.
registrarYesA registrar catalog slug of the nine, exactly (`name.com`, no `name-com` alias).

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.4/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 the safety profile is fully covered. The description contributes 'confirmed' (only confirmed changes, not proposed ones) and 'newest first' ordering, which is real context the schema does not carry. It stops short of noting result limits or pagination, so it is additive but not rich.

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 sentences, scope and ordering front-loaded, zero filler. It is arguably under-specified rather than bloated, which is a different problem than verbosity.

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 a simple two-parameter read with a full schema, an output schema and rich annotations, so most burden is carried elsewhere; the description covers scope and sort order. What is missing is disambiguation from the closely named price-change siblings, which matters given a 48-tool surface.

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 both `registrar` and `fields` are already documented, including the exact-slug and no-alias rule. The description's 'pass `registrar` (such as namecheap)' merely restates the requirement without adding syntax or constraints 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?

Names a specific resource with a clear scope: this registrar's confirmed list-price changes, ordered newest first. An agent can distinguish it from family-level siblings such as ud_list_price_changes or ud_list_registrar_prices because the registrar scoping is explicit. It is a noun phrase rather than a verb, but the operation is unambiguous.

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

Usage Guidelines3/5

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

The required `registrar` parameter implies the usage context (a single-registrar price-change history), but the description never states when to prefer this over ud_list_price_changes or ud_list_registrar_prices, nor any exclusions. Usage is inferable rather than taught.

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