Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Open auction of one name, if any

ud_get_name_auction
Read-onlyIdempotent

Retrieves the current open auction for a domain name, including venue, deadline, current bid, and first-year cost. Use it to check whether a name is at auction now or when bidding ends.

Instructions

The open auction of one name, if any: venue, deadline, bid and the first-year cost. Use it when someone asks whether a name is at auction now, its current bid or its deadline. Pass name (such as get.plumbing).

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

Input Schema

NameRequiredDescriptionDefault
nameYesA full domain name on an ending the catalog holds, lowercased, IDN as punycode. A bare word, a subdomain, an e-mail address or an unknown ending answers 400 `validation_failed` with `reason` and `suggestion`.
fieldsNoComma-separated top-level keys to keep: venue, venueLabel, endsAt, bid, bidCount, currency, firstYear, bidsJumped.

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/5.0
Behavior4/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 description adds the meaningful nuance 'if any' — signaling a possible empty/no-auction result — which is behavior not encoded in annotations or schema. It stops short of describing the no-auction response shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: what it returns, when to call it, and how to pass the argument — in that order, with zero filler. Every clause carries information the agent needs.

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 an output schema present and rich annotations plus full schema coverage, the description need not explain return values or errors. It covers purpose, trigger and argument format adequately; only the projection parameter and the null-result representation are unaddressed by the prose.

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 the schema already documents the domain-name format, lowercasing, punycode rules and validation failure behavior. The description adds only a format example ('get.plumbing') and is silent on the `fields` projection parameter, so it does not meaningfully exceed the schema.

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 and resource ('the open auction of one name') and enumerates the returned facets (venue, deadline, bid, first-year cost), so an agent knows exactly what it fetches. It does not explicitly name a sibling such as ud_get_market_auctions for market-wide auction data, so the differentiation is implied by 'one name' rather than stated.

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 explicit triggering questions: whether a name is at auction now, its current bid, or its deadline. That is a clear when-to-use context, but there are no exclusions or named alternatives for adjacent needs (e.g. domain availability via ud_get_name or market-wide auctions).

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