Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Domain sales pulse as headline aggregates

ud_get_market_sales
Read-onlyIdempotent

Get aggregate domain sales trends by window, price band, and sold-before count to assess overall market performance.

Instructions

The domain sales pulse as headline aggregates: windows, price bands and the sold-before count. Use it when someone asks how the domain sales market is doing overall. 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_get_market_sales"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: freshness, pulse, soldBefore.

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

B3.4/5.0
Behavior3/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds useful aggregate content but inaccurately says 'Takes no input' despite the optional fields parameter, and it does not discuss permissions or rate limits.

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?

The description is two sentences, front-loaded with the resource and aggregate contents, with no wasted wording. The final sentence is concise but inaccurate, which slightly reduces its quality.

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?

This is a low-complexity read tool with an output schema and rich annotations, so the description need not explain return values. However, it omits the optional fields projection and misstates that the tool takes no input, leaving a small but real completeness gap.

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 schema documents the optional fields projection parameter. The description says 'Takes no input,' which conflicts with that optional parameter and adds no meaning beyond the schema; this could mislead an agent into omitting a valid projection.

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 states a specific resource and scope: the domain sales market overall, with headline aggregates covering windows, price bands, and sold-before count. It does not name sibling breakdown tools, so differentiation from tools like ud_get_market_sales_lengths or ud_get_market_sales_word is only implicit through 'overall'.

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 explicitly says to use this when someone asks how the domain sales market is doing overall, which gives clear usage context. It does not state when not to use it or name alternative sibling tools for more specific 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