Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Registrar identities and the auction venue and parking service catalogs

ud_get_meta_providers
Read-onlyIdempotent

Fetches registrar identities plus auction venue and parking service catalogs to identify every provider a domain answer may name. Optionally limits results to specified top-level fields.

Instructions

Registrar identities and the auction venue and parking service catalogs. Use it when someone needs every registrar, auction venue and parking service an answer may name. 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_meta_providers"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: registrars, auctionVenues, parkingServices.

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.2/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. The description adds that this is a complete enumeration rather than a single lookup, but offers nothing on response shape or size for what is likely a large catalog, and output schema is left to carry that.

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, front-loaded with the resource scope and followed by the usage cue. The final 'Takes no input' clause is brief but earns no place because it is misleading rather than informative.

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?

With a rich annotation set and an output schema, the description does not need to explain return values, and it does not. The gap is that its one statement about input contradicts the actual schema, leaving the agent with a wrong model of the tool's call surface for a catalog tool that may return many records.

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 single optional `fields` parameter is fully documented in the schema, so baseline would be 3. But the description asserts 'Takes no input', which is inaccurate for a tool that accepts an optional projection parameter, actively steering the agent away from a useful capability.

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 three resources returned (registrar identities, auction venue catalog, parking service catalog) and signals completeness with 'every registrar, auction venue and parking service an answer may name'. That scope wording distinguishes it in spirit from narrower siblings like ud_list_market_auction_venues, though no sibling is named explicitly and the tool has no leading verb.

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?

It gives a positive usage cue ('Use it when someone needs every registrar, auction venue and parking service'), which implies it is the exhaustive-enumeration option rather than a lookup. However, it names no alternative and states no when-not condition, so the agent must infer routing from sibling names alone.

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