Skip to main content
Glama
Sign In
Unique Domains MCP server

Unique Domains MCP server

Official
by UniqueDomains
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

IANA registrar list as stored, by IANA id

ud_list_iana_registrars
Read-onlyIdempotent

Lists IANA registrars one page at a time, with optional status filtering, field selection, and cursor-based pagination for looking up accredited, terminated, or reserved registrars.

Instructions

The IANA registrar list as stored, by IANA id. Use it when someone asks for accredited registrars beyond the nine compared; it answers one page at a time. Every input is optional; limit sets the page size.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "ud_list_iana_registrars"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoPage size, 20 at most.
cursorNoThe `meta.cursor` of the previous page.
fieldsNoComma-separated top-level keys to keep: id, name, status, rdapBaseUrl.
statusNoIANA status.

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. Changed2 schema fields changedv0.1.5
    • changedOutput schema / properties / links / properties / details / description
      Previous value: -"The public Unique Domains page about the subject."New value: +"The public Unique.domains page about the subject."
    • changedOutput schema / properties / links / properties / product / description
      Previous value: -"The Unique Domains page that opens what a refusal named."New value: +"The Unique.domains page that opens what a refusal named."
  2. First observedv0.1.4

TDQS

A3.9/5.0
Behavior4/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 bar is lower. The description still adds useful behavior beyond them: results arrive one page at a time and every input is optional, which tells the agent to expect paginated enumeration rather than a full dump.

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 identity then usage then pagination, with no filler. 'Every input is optional' is mildly redundant with the zero-required-parameters schema but is cheap and clarifying.

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 not be described, and the schema covers all four filters. The description supplies the two things the schema can't: the relationship to the narrower registrar list and the paged nature of results.

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 the schema already explains limit, cursor, fields and status. The description only restates that inputs are optional and that limit is the page size, adding no format or interaction detail (e.g., how cursor relates to limit) beyond the schema.

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 resource (the IANA registrar list) and its ordering key (IANA id), and contrasts it with the curated set behind 'the nine compared', which points at the sibling list tool. 'As stored' is slightly vague about whether records are raw IANA rows, but the verb+resource are unambiguous.

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 wants accredited registrars beyond the nine already compared, which implicitly routes the agent away from the smaller curated list. It does not name that sibling explicitly or state when-not to use it, so a 5 isn't warranted.

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