Skip to main content
Glama
Sign In

Unique Domains

by domains.unique
OverviewDiscussionsAdmin

Nine registrars whose daily price lists are compared

ud_list_registrars
Read-onlyIdempotent

The nine registrars whose daily price lists are compared, in catalog order. Use it when someone asks which registrars the price comparisons cover. Takes no input.

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_registrars"
  }
}

Input Schema

NameRequiredDescriptionDefault
fieldsNoComma-separated top-level keys to keep: slug, name, kind, ianaId, accredited, homepageUrl, siteUrl, logoUrl, endingsPriced.

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

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so safety is covered. The description adds two useful facts beyond them: the result is a fixed nine-item set and it is returned in catalog order. However, 'Takes no input' is misleading because the schema exposes an optional 'fields' projection parameter, which the description never acknowledges.

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

Conciseness5/5

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

Three short sentences: identity/ordering first, then the use case, then the input expectation. Nothing is padded and the most decision-relevant information leads.

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 annotations carry the safety profile for this trivially simple, single-optional-parameter list tool. The only real omission is any hint that a 'fields' projection is available, and the unqualified 'Takes no input' slightly undercuts completeness.

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 'fields' parameter and its allowed keys are fully documented in structured data — baseline 3 applies. The description adds nothing about the parameter and in fact claims the tool takes no input, which mildly works against correct use rather than supporting it.

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?

States a specific resource — the fixed set of nine registrars covered by the daily price comparison — plus the ordering ('catalog order'). The qualifier 'whose daily price lists are compared' implicitly separates it from the IANA registrar list sibling, though it never names that sibling.

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?

Gives an explicit trigger: 'Use it when someone asks which registrars the price comparisons cover.' That is clear context for invocation. There is no exclusion clause or named alternative (e.g. ud_list_iana_registrars), so an agent must infer the boundary itself.

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