Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

A word's endings as stored on the latest day

ud_get_word_endings
Read-onlyIdempotent

A word's endings as stored on the latest day: counts, the key endings and the open names per ending. Use it when someone has a word and asks which endings are still open for it, such as harbor.ai or harbor.io. Pass word (such as harbor); 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": {
      "word": "<word>"
    },
    "name": "ud_get_word_endings"
  }
}

Input Schema

NameRequiredDescriptionDefault
wordYesThe catalog slug or the word.
fieldsNoComma-separated top-level keys to keep: byGroup, keyEndings, openByEnding, cheapest.

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. Changed1 schema field changed
    • changedInput schema / properties / word / description
      Previous value: -"The catalog slug, the word, or `wrd_<id>`."New value: +"The catalog slug or the word."
  2. First observed

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 scope, so the safety profile is covered. The description adds that results reflect a stored snapshot for the latest day, which hints at staleness, but it does not describe freshness windows, pagination, or behavior when the word is unknown.

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 sentences, front-loaded with what the tool returns and followed by the selection cue and a brief parameter note. No filler, though the opening phrase partly echoes the title.

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 carrying safety semantics, the description supplies what is needed: the resource, the snapshot scope, and the primary use case. The only soft gap is that the schema allows a catalog slug for `word` while the description only shows a plain word.

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 parameters are already documented in the schema. The description clarifies that `word` takes a bare word such as 'harbor' and that the other inputs are optional, but it never mentions `fields` or how it interacts with the returned keys — baseline applies since 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 names a specific verb and resource — retrieving a word's endings along with counts, key endings and open names per ending — scoped to 'the latest day'. It is clear what the tool returns, though it does not explicitly separate itself from siblings like ud_list_market_sales_endings or ud_resolve_word.

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 condition: use it when someone has a word and asks which endings are still open for it, with concrete examples (harbor.ai, harbor.io). No when-not-to-use or named alternative is provided, which keeps it below a 5.

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