Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Confirmed registrar price changes across the nine

ud_list_price_changes
Read-onlyIdempotent

List confirmed registrar price changes, newest first, to check which registrars adjusted prices recently. Optionally select returned fields.

Instructions

Confirmed registrar price changes across the nine, newest first. Use it when someone asks which registrar prices changed lately. 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 observedv0.1.4

TDQS

A3.5/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 closed-world, so the safety profile is covered. The description adds genuine value with the "confirmed" filter, "newest first" ordering and all-optional inputs, but says nothing about volume, truncation or pagination 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?

Three short sentences, front-loaded with the resource and ordering before the usage cue. The only wasted token is the opaque phrase "across the nine", which costs clarity without adding information.

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?

This is a simple read-only list tool with one optional parameter and an output schema, so return values do not need explaining. Nothing essential to invoking it correctly is missing, though the ambiguous "the nine" scope leaves the agent guessing about coverage.

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 `fields` parameter has 100% schema description coverage, so the schema does the work of listing the allowable keys. The description only contributes the general statement that every input is optional, which is a marginal addition beyond the schema.

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?

"Confirmed registrar price changes ... newest first" gives a specific resource plus ordering and a filter qualifier, which is more than a restated name. However, "across the nine" is unexplained and the description never distinguishes this from the closely named sibling ud_list_registrar_changes or ud_list_registrar_prices.

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?

"Use it when someone asks which registrar prices changed lately" supplies a concrete trigger condition. There is no exclusion or alternative named, which is a real gap given sibling names like ud_list_registrar_changes and ud_list_registrar_prices that plausibly answer overlapping questions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools