Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One-word catalog names under filters

ud_list_domains
Read-onlyIdempotent

List one-word domain names by filters such as ending, length, price, status, or style, returning paginated catalog results for domain research and selection.

Instructions

One-word catalog names under filters. Use it when someone wants one-word names matching filters such as ending, length or price. Neutral order, one page at a time. 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

NameRequiredDescriptionDefault
posNoComma 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.
limitNoPage size, 20 at most.
shapeNoComma list of word shapes: single, properNoun, acronym, twoWords, phrase. `properNoun` is ignored on the free tier.
styleNoComma list of styles: modern, elegant, slab, handwritten, playful, futuristic.
cursorNoThe `meta.cursor` of the previous page.
endingNoComma list of endings without the dot.
fieldsNoComma-separated top-level keys to keep: id, name, ending, status, price, priceKind, renewal, ratingBand, format, shape, length, coverage, value, upsidePercent, liquidity, verdict.
formatNoOne word, or domain hacks.
statusNoComma list of statuses: available, premium, resell, expiring, expired, taken, dormant, sold, unknown. Default: available, premium, resell.
priceMaxNoHighest price today, USD.
lengthMaxNoLongest word, in characters.
lengthMinNoShortest word, in characters.
renewalMaxNoHighest renewal, USD.
expiresBeforeNoRegistry expiry on or before this day.

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

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the bar is lower. The description still adds two genuinely useful facts not in structured data: results come back in "neutral order" (i.e., not ranked by relevance or price) and are paged "one page at a time", plus the statement that every input is optional. It stops short of explaining cursor mechanics or what the page envelope contains.

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?

Four short sentences with the resource stated first, then the use case, then ordering/pagination, then a parameter note — well front-loaded and free of filler. Minor waste: the opening sentence duplicates the tool title almost verbatim.

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 read-only annotations, a full output schema, and 14 fully documented optional parameters, the definition supplies what an agent needs to call it: purpose, trigger, ordering, pagination, and optionality. The remaining gap is disambiguation from overlapping listing tools (especially ud_list_domain_hacks) rather than any missing invocation detail.

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% and every one of the 14 properties carries its own description (including allowed status/shape/pos vocabularies and the free-tier caveat for `properNoun`), so the schema does the heavy lifting. The description's only parameter claim, that `limit` sets page size, merely restates the schema. Baseline 3 applies.

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?

"One-word catalog names under filters" names a specific resource (one-word domain names) and the filtering scope, and the when-to-use sentence reinforces it with concrete filter kinds (ending, length, price). It does not, however, distinguish itself from the sibling ud_list_domain_hacks, which overlaps with the `format: oneWord|hack` parameter exposed here.

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?

"Use it when someone wants one-word names matching filters such as ending, length or price" gives a clear positive trigger, which is better than nothing. There are no exclusions and no named alternative for the near-duplicate case (domain hacks, or the various ud_list_market_sales_* / ud_get_word_* tools), so the agent must infer which listing tool to pick.

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