Skip to main content
Glama

Domain registrar profile

registrar_info
Read-onlyIdempotent

Retrieve a domain registrar’s size, rank, abuse rate, compromised-domain count, and ID for downloading its full domain list. Search by brand, legal name, or numeric ID.

Instructions

Size, rank and abuse figures of a domain registrar: number of domains, rank by size, compromised domains and abuse rate versus the overall rate, link to the registrar page. Matches by brand ("GoDaddy"), legal name or numeric id. The returned id is what get_download_url takes as registrar_id for the list of all domains of the registrar. Free.

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

Input Schema

NameRequiredDescriptionDefault
queryYesRegistrar name, brand or id, e.g. "Namecheap"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by disclosing the returned fields, the accepted matching forms, the downstream id linkage, and the cost ('Free') — practical traits not present in the annotations.

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 dense sentences that lead with the returned data and end with matching rules and cost; nothing is wasted. Slightly information-packed but well front-loaded.

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 no output schema, the description compensates by enumerating the returned fields and explaining the id's downstream use in get_download_url. Matching behavior and cost are covered; minor gaps around ambiguous-name resolution would only matter at the margin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description meaningfully extends the parameter by stating that the query matches by brand name, legal name, or numeric id — richer semantics than the schema's example 'Namecheap' alone.

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?

Names the resource (domain registrar) and enumerates exactly what is returned: domain count, rank, compromised domains, abuse rate, and a link. It also distinguishes itself from siblings by specifying that the returned id is the input to get_download_url, so an agent can tell it apart from domain_rank or dns_provider_info.

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 clear context (looking up a registrar profile by brand/legal name/id) and explicitly routes to get_download_url for the full domain list, which is genuine when-to-use guidance. It does not state when NOT to use it versus nearby siblings like domain_rank or tld_stats, so it falls short of a 5.

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