Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Turns what a caller typed into the catalog word it names

ud_resolve_word
Read-onlyIdempotent

Resolve a typed, misspelled, plural, or unclear word to its catalog match or up to five candidates. Pass q first so word tools receive a valid catalog term.

Instructions

Turns what a caller typed into the catalog word it names, or up to five candidates. Use it first when a word is misspelled, plural or unclear, to find the catalog word the word tools take. Pass q (such as harbors).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "q": "<q>"
    },
    "name": "ud_resolve_word"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYesWhat the caller typed, 1 to 255 characters.
fieldsNoComma-separated top-level keys to keep: match, candidates.

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.8/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description contributes the ambiguity behavior ('or up to five candidates') and the sequencing expectation, which is genuine added value, but it does not say how matching works, whether candidates are ranked, or what happens when nothing matches.

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

Conciseness5/5

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

Two sentences, front-loaded with the transformation, then the when-to-use rule and the one parameter worth illustrating. Every clause earns its place and nothing is repeated for padding.

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 an output schema present and annotations covering safety and idempotency, the description need not explain return shape; it correctly limits itself to purpose, trigger and the candidate count. The one remaining gap is the absence of any guidance on `fields`, though the schema already enumerates its keys.

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 coverage is 100%, so both `q` and `fields` are already documented, including the allowed keys match/candidates. The description only adds an illustrative value ('such as harbors') for `q` and never mentions `fields`, so this is the baseline case where the schema does the heavy lifting.

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 states a specific transformation: typed input becomes 'the catalog word it names, or up to five candidates.' That is distinguishable from the ud_get_word_* siblings, which read properties of an already-known word, and the phrase 'the catalog word the word tools take' frames it as a resolver feeding those tools. The opening clause does largely restate the title, which keeps it just short of a 5.

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 an explicit trigger ('Use it first when a word is misspelled, plural or unclear') along with the ordering rationale, so an agent knows to call this before the word-property tools. It does not state the inverse case — skip this when the word is already an exact catalog match — but that condition is strongly implied by the trigger.

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