Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Keywords the catalog attaches to the ending, by type

ud_list_tld_keywords
Read-onlyIdempotent

The keywords the catalog attaches to the ending, by type. 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 observed

TDQS

C2.7/5.0
Behavior2/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 covered. The description adds nothing beyond that: no note on result size, whether every TLD has keywords, or what an empty result means. There is no contradiction, but there is no added behavioral value either.

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?

Two short sentences, front-loaded, with no wasted clauses. It loses a point only because the first sentence duplicates the title verbatim rather than leveraging the space to add routing or behavioral information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 fully documented parameters, the definition is callable as-is. It remains incomplete on the selection side: nothing explains the relationship to the many sibling lookup tools, which is the main ambiguity for an agent choosing among ud_* tools.

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 the schema itself explains normalization ('without the dot', 'xn-- form, lowercased'), the type enum, and the comma-separated fields list. The description only echoes this by naming `tld` and calling the rest optional, so baseline 3 applies.

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 is essentially the title restated: it names the resource (keywords the catalog attaches to an ending) and the grouping (by type), but supplies no verb such as 'list' or 'returns' and does not distinguish it from siblings like ud_get_word_endings or ud_get_tld. An agent can infer it is a lookup keyed on a TLD, but the purpose is only implied rather than asserted.

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?

The only guidance is 'Pass `tld` (such as ai); the other inputs are optional', which restates required-vs-optional information already in the schema. There is no statement of when to reach for this tool, when not to, or which sibling (ud_get_word_endings, ud_get_tld, ud_list_word_categories) covers the adjacent need.

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

All Unique Domains toolsInspect
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.

Resources