Skip to main content
Glama

Statistics of a domain zone (TLD)

tld_stats
Read-onlyIdempotent

Retrieve detailed statistics for one TLD, including registry, active domains, new and deleted domains, growth trends, rank, abuse rate, Top 1M presence, policies, and RDAP data.

Instructions

Everything NetAPI knows about one TLD: registry, number of active domains, new and deleted domains in the last 24 hours, growth over 7/30/90/365 days, rank among all 1,584 zones, share of all domains, compromised domains and abuse rate, presence in the Top 1M, registry policies, RDAP server and a description. 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": {
      "tld": "<tld>"
    },
    "name": "tld_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
tldYesTLD without the dot, e.g. "com", "de", "xn--p1ai"

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 real context beyond that: it is free, it exposes data freshness windows (last 24 hours, growth over 7/30/90/365 days), and it enumerates the breadth of the response. It does not state whether the TLD must exist or what happens on an unknown zone.

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?

Front-loaded with the purpose ('Everything NetAPI knows about one TLD') followed by a compact field enumeration. The list is long but each item defines scope for a tool with no output schema, so it earns its place; the trailing 'Free.' is the only low-value fragment.

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 field enumeration is the agent's only preview of return values, and it is thorough (registry, counts, growth windows, rank, abuse, policies, RDAP). For a single-parameter read tool with full annotation coverage, what remains missing is minor: error behavior for invalid TLDs and pagination/size expectations.

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% and the single 'tld' parameter is well documented in the schema, including format examples ('com', 'de', 'xn--p1ai'). The description adds nothing about the parameter, which is the expected baseline when the schema does the work.

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 gives a specific resource ('one TLD') and enumerates exactly what is retrieved: registry, active domain counts, new/deleted in 24h, growth windows, rank among 1,584 zones, abuse rate, RDAP server. An agent can tell this is a per-TLD aggregate lookup. It does not explicitly distinguish itself from siblings like domain_rank, registrar_info or list_zones, which keeps it from a 5.

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

Usage Guidelines2/5

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

No when-to-use guidance and no alternatives are named, so the agent gets no help choosing between this and domain_rank, registrar_info or top_1m. The trailing 'Free.' is the only usage-relevant note, signalling no cost barrier, which is marginal.

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