Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

A word's stored sales and auction aggregates

ud_get_word_market
Read-onlyIdempotent

Retrieve a word's stored sales and auction aggregates across domain endings, including counts, prices, and open auctions, to see how that word sells.

Instructions

A word's stored sales and auction aggregates. Use it when someone asks how a word sells across endings: counts, prices and auctions. Pass word (such as harbor).

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

Input Schema

NameRequiredDescriptionDefault
wordYesThe catalog slug, the word, or `wrd_<id>`.
fieldsNoComma-separated top-level keys to keep: sales12m, sales30d, medianFromThree, endingsSoldOn, openAuctionsByEnding.

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 declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The word 'stored' hints that these are precomputed aggregates rather than live figures, but the description never states freshness, currency/units for prices, or what an empty result means.

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 definition before the usage hint and the parameter call-out. The opening sentence duplicates the title verbatim, which is the only wasted text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 input schema fully documents both parameters. What remains is purpose, trigger and an example — all present for a low-complexity read-only lookup.

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%, so both `word` and `fields` are fully documented in the schema. The description only adds an example value ('such as harbor') for `word` and says nothing about the `fields` projection parameter, so it stays at the baseline.

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 a concrete resource ('a word's stored sales and auction aggregates') and enumerates what it covers (counts, prices, auctions), which is more specific than the title alone. It does not differentiate itself from the near-identically named sibling `ud_get_market_sales_word`, so an agent must infer the split.

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?

There is a real usage trigger: 'Use it when someone asks how a word sells across endings.' However, no when-not condition or alternative tool is named, which is notable given siblings like `ud_get_market_sales_word` and `ud_get_word_endings` that plausibly overlap.

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