Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Registrar identities and the auction venue and parking service catalogs

ud_get_meta_providers
Read-onlyIdempotent

Registrar identities and the auction venue and parking service catalogs. 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 observed

TDQS

C2.3/5.0
Behavior2/5

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

Annotations already declare read-only, idempotent, closed-world and non-destructive, so the safety profile is covered without the description. The description adds nothing beyond that and its claim 'Takes no input' misrepresents the tool's actual input surface, leaving no useful behavioral context.

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

Conciseness2/5

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

The first sentence duplicates the title verbatim, adding no information, and the second sentence is factually wrong given the optional `fields` parameter. Short, but both sentences fail to earn their place because one is redundant and one is misleading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/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 values need no explanation, but the description still fails to convey that this is an aggregate reference-data endpoint versus the individual sibling listings. The false 'Takes no input' claim leaves the agent with an incomplete and partially incorrect mental model.

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 (comma-separated top-level keys), so the description need not explain it. Worse, the description actively contradicts it by asserting 'Takes no input', which could cause an agent to miss the projection option.

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

Purpose3/5

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

The description names the resources (registrar identities, auction venues, parking services) but is a noun phrase rather than a verb+resource statement, and it does not distinguish this aggregate meta endpoint from siblings like ud_list_registrars or ud_list_venues. 'Registrar identities' is also vaguer than what the tool likely returns.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this versus the many sibling list/get tools that overlap (ud_list_registrars, ud_list_venues, ud_get_meta_enums). The only usage-like statement is 'Takes no input', which is not routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Unique Domains toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources