Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Domain hacks

ud_list_domain_hacks
Read-onlyIdempotent

List domain hacks—short names whose ending spells the final letters of a word—with filters for ending, length, price, status, and style.

Instructions

Domain hacks: names whose ending completes the word. Use it when someone wants a short name in which the ending spells the last letters of the word. 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_domain_hacks"
  }
}

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.
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.6/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 a closed world, so the safety profile is fully covered. The description adds only that every input is optional and that `limit` is the page size, which is thin; it says nothing about what the default status filter does or how the cursor paging behaves beyond what the schema states.

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?

Three short sentences, front-loaded with the domain-hack definition before the usage trigger. The final clause about `limit` is redundant with the schema and could be dropped, but the overall text is tight.

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 13 fully documented optional parameters and an output schema, the description's main burden is explaining the concept and optionality, which it does. It stops short of explaining default filtering (default statuses) or result ordering, but those gaps are largely filled by the schema and output schema.

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%, including enum-like value lists, defaults and ranges, so the baseline is 3. The description's only parameter statement ('Every input is optional; `limit` sets the page size') restates schema facts rather than adding filtering semantics or combination behavior.

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 defines the resource precisely: names whose ending completes a word, which is a distinct concept from the general domain listing in ud_list_domains. It lacks an explicit verb (list/search) and never names a sibling, but the defining clause is specific enough that an agent can tell what comes back.

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?

It gives a concrete trigger: 'Use it when someone wants a short name in which the ending spells the last letters of the word.' That clearly separates this from a plain domain search, but no exclusions or named alternatives are provided for cases where the user wants, say, ending-based market sales data.

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