Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

One applied-for string

ud_get_tld_application_string
Read-onlyIdempotent

Retrieves one applied-for TLD string with its applications and change history, so you can see who applied for a specific ending.

Instructions

One applied-for string: its applications and its change history. Use it when someone asks about one applied-for ending, such as who applied for it. Pass string (such as account).

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": {
      "string": "<string>"
    },
    "name": "ud_get_tld_application_string"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: string, applications, changes.
stringYesThe applied-for string, lowercased ASCII (an IDN as its A-label).

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 openWorldHint=false, so the safety profile is fully covered. The description adds only the contents of the response (applications plus change history), with no note on result size, ordering, or whether history is paginated.

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 the result contents before the usage cue. The trailing "Pass `string` (such as account)" is somewhat redundant given the schema, but the text is tight overall.

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 description still summarizes the two payload sections. The unmentioned `fields` selector is covered in the schema, leaving little an agent would need and not have.

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%, so both `string` and `fields` are already documented in the schema. The description's example value "account" is a mild illustration, but it never mentions the `fields` projection parameter, so it adds little beyond structured data.

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 resource — a single applied-for string — and enumerates what it returns: its applications and its change history. That distinguishes it from the plural siblings such as ud_list_tld_applications and ud_list_tld_changes, though it does not name them explicitly.

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 asks about one applied-for ending, such as who applied for it." The emphasis on "one" implicitly routes multi-record lookups elsewhere, but no exclusion or named alternative is stated.

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