Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Up to ten words whose sales moved over the last 30 days

ud_list_market_sales_movers
Read-onlyIdempotent

Lists up to ten words whose sales changed over the last 30 days, indicating which words are selling more or less. Takes no input.

Instructions

Up to ten words whose sales moved over the last 30 days. Use it when someone asks which words are selling more or less lately. 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_movers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: word, sales30d, prev30d, direction, sales90d, median12mUsd, prevMedian12mUsd, endingsSoldOn.

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 openWorldHint=false, so the safety profile is covered. The description adds the result cap ('up to ten') and the 30-day window, which is useful. It does not say how movers are ranked or ordered, which is the main behavioral question an agent would have.

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?

Three short sentences, front-loaded with the resource and window, then the usage trigger, then the input note. No filler or redundancy.

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?

An output schema exists, so return values need not be explained, and the annotations cover safety. The remaining gap is the misleading 'Takes no input' claim against a real optional parameter, plus no statement of ordering or how 'moved' is computed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single optional 'fields' parameter is fully documented in the schema, so the baseline would be 3. However, the description asserts 'Takes no input,' which is inaccurate given the optional fields projection parameter, actively steering the agent away from a usable capability.

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?

States a specific resource (words) and a specific metric (sales movement over the last 30 days), plus the cap of ten results. It is distinguishable from siblings like ud_list_market_sales_endings or ud_list_market_sales_series by the 'movers' framing, though it never names an alternative explicitly.

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?

Gives a clear trigger: 'Use it when someone asks which words are selling more or less lately.' That maps a user intent to the tool well. It stops short of exclusions or pointing to sibling tools for related questions (e.g. endings or series breakdowns).

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