Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

IANA registrar list as stored, by IANA id

ud_list_iana_registrars
Read-onlyIdempotent

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. Changed1 schema field changed
    • changedInput schema / properties / limit / maximum
      Previous value: -100New value: +20
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare read-only, idempotent, non-destructive and closed-world, so the description earns credit for the pagination behavior it adds: 'answers one page at a time' and 'limit sets the page size'. It does not cover default page size or how the cursor terminates, but the output schema carries the return shape.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences with the resource stated first, which is well front-loaded. However, the opening repeats the title nearly verbatim, and the 'nine compared' clause is wasted words that raise a question without answering it.

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 a full output schema and rich annotations, the description only needs to convey scope and pagination, both of which it does. The one genuine gap is the undefined comparison set implied by 'the nine compared', which an agent cannot resolve from the definition.

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 every parameter including limit, cursor, fields and the status enum is already documented. The description only paraphrases limit as page size and notes that all inputs are optional, adding nothing beyond the schema. Baseline 3 applies.

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?

Names the resource ('the IANA registrar list') and the ordering key ('by IANA id'), which is more than the title restates. It does not name a sibling to distinguish from, and 'beyond the nine compared' is an unexplained reference that leaves some ambiguity about scope.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Offers one usage cue ('when someone asks for accredited registrars beyond the nine compared'), which implies a relationship to some comparison set but never names an alternative tool or the condition that selects it. No when-not guidance; the reader cannot tell how it differs from ud_list_registrars.

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