Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Day's fixed sample of up to 20 single-word names at auction

ud_list_market_auctions_sample
Read-onlyIdempotent

List a fixed daily sample of up to 20 single-word domain auctions with ending deadlines to show examples of names at auction today; optionally choose returned fields.

Instructions

The day's fixed sample of up to 20 single-word names at auction, by deadline. Use it when someone wants examples of single-word names at auction today. A fixed daily sample, not every auction. 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_auctions_sample"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: name, ending, venue, venueLabel, endsAt, currency, bid, bidCount, verdict, firstYear, tag.

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

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the description's job is to add behavioral caveats — it does, disclosing that the result is a fixed capped sample (max 20) and not a complete enumeration, which matters for downstream reasoning about completeness. The ordering cue ('by deadline') is a useful extra. Minor tension: 'Takes no input' sits awkwardly beside the optional fields parameter.

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 and scope, and the cap/limits warning comes early. Slightly wasteful phrasing between the title echo and the closing 'Takes no input,' which is also mildly at odds with the optional param.

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?

A low-complexity sampling tool with an output schema, so return values need no explanation; the description still covers scope, cap size, ordering, and daily-fixed nature. What is missing is only a pointer to the full-auction sibling for non-sample needs.

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% and the single optional 'fields' projection parameter is fully documented in the schema. The description adds nothing about it and in fact says 'Takes no input,' which could lead an agent to overlook the projection option, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: 'The day's fixed sample of up to 20 single-word names at auction, by deadline.' It explicitly separates itself from broader auction listings with 'A fixed daily sample, not every auction,' so an agent can distinguish it from ud_get_market_auctions without opening the schema.

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 use condition: 'Use it when someone wants examples of single-word names at auction today.' The 'not every auction' line implicitly routes bulk/complete needs elsewhere, but no sibling is named explicitly, so the alternative path must be inferred.

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