Unique Domains

One-word catalog names under filters

ud_list_domains

Read-onlyIdempotent

One-word catalog names under filters. Every input is optional; limit sets the page size.

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_domains"
  }
}

Input Schema

Name	Required	Description
`pos`	No	Comma list of parts of speech: adjective, adjective satellite, adverb, conjunction, contraction, determiner, interjection, letter, noun, particle, pnoun, pnound, preposition, prepPhrase, pronoun, proverb, symbol, verb, unknown.
`limit`	No	Page size, 20 at most.
`shape`	No
`style`	No	Comma list of styles: modern, elegant, slab, handwritten, playful, futuristic.
`cursor`	No	The `meta.cursor` of the previous page.
`ending`	No	Comma list of endings without the dot.
`fields`	No	Comma-separated top-level keys to keep: id, name, ending, status, price, priceKind, renewal, ratingBand, format, shape, length, coverage, value, upsidePercent, liquidity, verdict.
`format`	No	One word, or domain hacks.
`status`	No	Comma list of statuses: available, premium, resell, expiring, expired, taken, dormant, sold, unknown. Default: available, premium, resell.
`priceMax`	No	Highest price today, USD.
`lengthMax`	No	Longest word, in characters.
`lengthMin`	No	Shortest word, in characters.
`renewalMax`	No	Highest renewal, USD.
`expiresBefore`	No	Registry expiry on or before this day.

Output Schema

Name	Required	Description
`data`	No
`meta`	No	The day of the answer, and the page cursor of a list.
`links`	No	Links of the answer.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

C2.8/5.0

Behavior3/5

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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds that no filters are required and mentions page size, but does not explain pagination via cursor, default status filtering, or how filters combine.

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?

It is very short and front-loads the resource description, with no wasted wording. However, the phrase 'catalog names under filters' is somewhat cryptic and could be more explicit.

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?

For a 14-parameter filtering/list endpoint, the description is too thin. Even with rich schema descriptions, annotations, and an output schema, it fails to clarify what 'one-word catalog names' means, how it relates to domain hacks, or expected filtering behavior.

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 93%, so the schema already documents nearly all parameters in detail. The description only mentions limit, adding no meaningful semantics beyond the schema baseline.

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 identifies the resource as 'One-word catalog names under filters,' which gives some sense of the output. However, it omits an explicit verb and does not distinguish this tool from siblings like ud_list_domain_hacks or ud_get_domain, leaving the exact purpose somewhat vague.

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?

It states that every input is optional and that limit sets page size, but provides no guidance on when to use this listing tool instead of related siblings. There are no exclusions or alternative-selection criteria.

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

All Unique Domains tools Inspect

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.