Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

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

ud_list_registrar_changes
Read-onlyIdempotent

Retrieve a registrar's confirmed list-price changes, newest first, to track how prices shifted recently. Pass the registrar slug to see old and new prices with confirmation dates.

Instructions

A registrar's confirmed list-price changes, newest first. Use it when someone asks how one registrar's prices changed lately. 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 observedv0.1.4

TDQS

A3.6/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world). The description adds two useful behavioral facts beyond them: results are limited to 'confirmed' changes and are sorted newest first. However, 'lately' leaves the default time window undefined, and there is no mention of result limits or pagination.

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 with the scope, trigger, and required argument in that order — front-loaded and easy to scan. The only waste is the registrar example, which duplicates an enum value already in the schema.

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?

For a low-complexity, two-parameter read tool with an output schema and full annotation coverage, the description is nearly sufficient. The remaining gaps are the undefined 'lately' default window and no statement about result caps or ordering ties.

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%, with the registrar enum, the exact-slug requirement, and the `fields` projection key all documented inline. The description's 'Pass registrar (such as namecheap)' only restates the required-field fact and an example already present in the enum, so it adds little 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?

The first sentence states a specific resource and scope: confirmed list-price changes for a single registrar, returned newest first. That distinguishes it from a generic all-registrar price-change listing, though it never names the sibling tool an agent should compare against.

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

Usage Guidelines4/5

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

It gives a concrete trigger — 'when someone asks how one registrar's prices changed lately' — which tells the agent the request shape this tool answers. It stops short of exclusions or naming the alternative for cross-registrar or unconfirmed price 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