Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Each ending's 12-month and 30-day sales figures

ud_list_market_sales_endings
Read-onlyIdempotent

Lists domain ending sales for the past 12 months and 30 days, with counts and median USD prices, so you can compare which endings sell and at what price.

Instructions

Each ending's 12-month and 30-day sales figures, alphabetical. Use it when someone asks which endings sell and at what median price. Takes no input.

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

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: ending, count12m, median12mUsd, prevCount12m, prevMedian12mUsd, trendWord, count30d, median30dUsd.

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. Changed2 schema fields changedv0.1.5
    • changedOutput schema / properties / links / properties / details / description
      Previous value: -"The public Unique Domains page about the subject."New value: +"The public Unique.domains page about the subject."
    • changedOutput schema / properties / links / properties / product / description
      Previous value: -"The Unique Domains page that opens what a refusal named."New value: +"The Unique.domains page that opens what a refusal named."
  2. 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 declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered elsewhere. The description contributes useful behavioral detail (alphabetical ordering) but nothing on volume, pagination, or how large the ending list is. Note the phrase "Takes no input" sits awkwardly against the schema's optional fields parameter, though it does not contradict any annotation.

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, front-loaded with the payload description and then the usage trigger; there is no filler. The trailing 'alphabetical' is slightly stranded but still earns its place as ordering 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?

An output schema exists, so return-value detail is unnecessary, and for a no-required-parameter listing tool the description covers what it returns and when to reach for it. The only gap is that it neither acknowledges the optional fields projection nor differentiates itself from the other market-sales list tools.

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% and the single optional fields parameter is fully documented with its allowed keys, so baseline is 3. The description adds nothing about the projection parameter and arguably implies it does not exist, which mildly undercuts rather than extends 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 description names the resource precisely (per-ending 12-month and 30-day sales figures) and adds the ordering (alphabetical) plus the median-price dimension, so an agent knows exactly what comes back. It stops short of distinguishing itself from close siblings such as ud_list_market_sales_series or ud_list_market_sales_movers, so it is clear but not disambiguating.

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?

"Use it when someone asks which endings sell and at what median price" gives a concrete triggering intent that maps directly to the tool's payload. There are no stated exclusions or named alternatives, which is the only thing separating this from a top score.

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