Skip to main content
Glama

ICANN Registrar Directory

registrar
Read-onlyIdempotent

Look up ICANN-accredited registrars by name, alias, or IANA ID. Returns accreditation status, RDAP endpoint, business contact details, a drop-catch flag, and the parent entity for reseller shells. Around 60 percent of accredited registrars are shells operated by a handful of parents, so parent_id is what tells you who actually runs a name.

Related: whois, available, expired.

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": {
      "query": "<query>"
    },
    "name": "registrar"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number for pagination
queryYesRegistrar name, alias, or IANA ID (e.g. 'namecheap', 'gname', '1441')

Output Schema

NameRequiredDescriptionDefault
dataNoMatching registrars
pageNo
errorNo
totalNoRows on this page
successNo
max_pageNo
total_foundNoTotal matches across all pages

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Changed1 schema field changed
    • changedOutput schema / properties / data / items / properties / rdap_fetched / description
      Previous value: -"False means the RDAP record could not be retrieved this time (time budget or upstream). It does NOT mean the registrar has no address on file"New value: +"False means the RDAP record could not be retrieved this time (time budget or source unavailable). It does NOT mean the registrar has no address on file"
  3. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuinely non-obvious domain behavior: that ~60% of accredited registrars are reseller shells and that parent_id identifies the true operator, which changes how results should be interpreted. It stops short of describing pagination or empty-result behavior.

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 sentences, each earning its place: capability, return payload, and the interpretive insight about parent entities, followed by a compact sibling pointer. Front-loaded with the action verb and free of padding.

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 the description need not fully specify return values, and annotations carry the safety profile. What remains is minor: pagination semantics and any rate/auth notes are unstated, but nothing blocks correct invocation for a two-parameter read tool.

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 baseline is 3. The description restates the query semantics already present in the schema ('name, alias, or IANA ID') and adds no syntax detail; the page parameter is entirely unaddressed in the description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb plus resource: 'Look up ICANN-accredited registrars by name, alias, or IANA ID.' It also enumerates the returned fields (accreditation status, RDAP endpoint, contacts, drop-catch flag, parent entity), so the agent can distinguish this directory lookup from whois or availability tools at a glance.

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?

'Related: whois, available, expired' points at neighboring tools but attaches no conditions, so it never states when to choose registrar over whois or when to chain them. The usage context is implied rather than prescribed, and there is no guidance on paginating via the page parameter.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.