Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Keywords the catalog attaches to the ending, by type

ud_list_tld_keywords
Read-onlyIdempotent

Lists keywords and topics attached to a domain ending by type, so you can check which words a TLD such as ai suits. Pass the TLD; filter by facet or field.

Instructions

The keywords the catalog attaches to the ending, by type. Use it when someone asks which words or topics an ending suits. Pass tld (such as ai); the other inputs are optional.

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": {
      "tld": "<tld>"
    },
    "name": "ud_list_tld_keywords"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesThe ending without the dot (`ai`), ASCII or `xn--` form; lowercased, a leading dot stripped.
typeNo`semantic` or one facet.
fieldsNoComma-separated top-level keys to keep: type, keyword, power.

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 readOnly, idempotent, non-destructive and openWorld=false, so the safety profile is fully covered elsewhere. The description adds only that the non-`tld` inputs are optional, which is parameter-level rather than behavioral. Nothing is said about ordering, completeness of results, or empty-result behavior for endings with no attached keywords.

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 what the tool returns before the usage cue and the required input. No filler. The opening sentence largely restates the title, which is the only redundancy.

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?

An output schema exists, so return values need no explanation, and the tool is a simple filtered list. The description covers the resource, the trigger, and the required input. It could still mention what an empty response means when an ending has no keywords of a given type, but nothing critical is missing.

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%, with the `tld` normalization rules, the type enum, and the field filter all documented inline. The description contributes only an illustrative value (`ai`) and the fact that only `tld` is required, both already derivable from the schema. Baseline 3 is appropriate.

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?

States the specific resource — the keywords the catalog attaches to a given ending — and that they are grouped by type. It is clear what data comes back, though the phrasing mirrors the title and never uses an explicit verb like 'list' to signal the operation. Sibling tools like ud_list_word_categories are not distinguished from it.

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?

Gives an explicit usage trigger: 'Use it when someone asks which words or topics an ending suits.' That maps a user intent directly onto this tool. It stops short of naming when-not-to-use or pointing at an alternative, so it is clear context without exclusions.

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