Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One word's sales market over 12 months

ud_get_market_sales_word
Read-onlyIdempotent

Retrieve a word's 12-month sales market data—count, median price, endings sold on, and latest sale month—to answer how that word has sold over the past year.

Instructions

One word's sales market over 12 months: count, median, endings sold on and the latest sale's month. Use it when someone asks how one word has sold over the last year. Pass word (such as hive).

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": {
      "word": "<word>"
    },
    "name": "ud_get_market_sales_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYesThe word, 2 to 63 lowercase letters, digits or inner hyphens.
fieldsNoComma-separated top-level keys to keep: status, word, sales12m, median12mUsd, endingsSoldOn, lastSaleMonth.

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 readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the content of the result (count, median, endings sold on, latest month), but since an output schema exists that is largely redundant rather than new behavioral context.

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 tight sentences with the resource definition front-loaded and the usage cue second; the example call at the end is useful. The opening clause nearly duplicates the title, which is mild waste.

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?

With annotations, an output schema and full schema descriptions, the definition covers what the tool is and when to call it. The only soft spot is silence on whether results can be empty for words with no sales in the window.

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 coverage is 100%, so both `word` and `fields` are already documented with formats and allowed keys. The description only reiterates `word` with an example ('such as hive') and does not explain the `fields` projection parameter at all — 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?

States a specific verb+resource+scope: the sales market for ONE word over 12 months, and enumerates what it returns (count, median, endings sold on, last sale month). The 'one word' qualifier implicitly separates it from the aggregate market tools, though no sibling is named.

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 how one word has sold over the last year' gives a concrete triggering question. No exclusion cases or named alternatives, so it is clear context without routing guidance.

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