Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Today's domain auctions by venue

ud_get_market_auctions
Read-onlyIdempotent

Retrieve today's domain auction market data by venue, closing time, length, and next seven days, with tracked counts. Use it for a whole-market overview.

Instructions

Today's domain auctions by venue, ending and length, the next seven days and the tracked counts. Use it when someone asks about today's auction market as a whole. 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_auctions"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: day, closing, withBid, counts, byVenue, byEnding, byLength, next7Days.

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 readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds the temporal scope (today plus the next seven days) and the aggregate nature of the result, but says nothing about freshness semantics, whether 'today' is UTC-based, or how counts are derived. 'Takes no input' is also at odds with the optional projection parameter, which could mislead an agent.

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 with no padding, and the usage condition is front-loaded. The first sentence is a comma-chained fragment ('by venue, ending and length, the next seven days and the tracked counts') that costs some readability.

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 description is unnecessary, and the description covers scope, dimensions, and the invocation mode. What remains thin is the definition of 'tracked counts' and the projection parameter, but these are minor for a read-only aggregate endpoint.

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 'fields' parameter enumerates its allowed keys, so the schema carries the semantics and the baseline of 3 applies. The description does not explain the projection behavior and instead asserts 'Takes no input', which subtly discourages use of the one parameter the schema exposes.

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 (today's domain auctions) and enumerates its dimensions — by venue, ending, length, next seven days, tracked counts — which is enough for an agent to recognize the aggregate-report tool. It is a noun-phrase fragment rather than a clean verb+resource statement, and the sibling differentiation comes only indirectly through 'as a whole' rather than any named tool.

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?

The sentence 'Use it when someone asks about today's auction market as a whole' gives a clear selection rule and implicitly contrasts with per-domain or per-venue lookups. It stops short of naming an alternative sibling or stating when not to use it, so it does not reach the explicit-alternatives tier.

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