Skip to main content
Glama

List all domain zones (TLDs)

list_zones
Read-onlyIdempotent

List all TLD zones tracked by NetAPI with active, new, and deleted domain counts, ccTLD status, and daily-update flags; filter by minimum domain size or ccTLD/gTLD.

Instructions

Every TLD NetAPI tracks (1,584 zones) with active domains, new and deleted domains in the last 24 hours, whether it is a ccTLD and whether it is updated daily. Filter by minimum size or ccTLD / gTLD. Free.

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": "list_zones"
  }
}

Input Schema

NameRequiredDescriptionDefault
cctldNotrue = country-code zones only, false = generic zones only
min_domainsNoOnly zones with at least this many active domains

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds genuinely useful context beyond them: the dataset size (1,584 zones), the freshness window (last 24 hours) and the 'Free' cost signal.

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?

Three tight sentences with no filler; the resource scope leads and the filter/cost notes follow. Slightly dense grouping of return fields, but every clause carries information.

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?

For a zero-required-parameter, read-only list tool with annotations covering safety, the description supplies the missing pieces: what is returned, how fresh it is, dataset size, and cost. No output schema exists, yet the field list largely compensates.

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 both parameters are already documented in the schema. The description restates the same filter semantics ('minimum size', 'ccTLD / gTLD') without adding format, interaction, or edge-case detail, so the baseline of 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 a specific resource (all TLD zones NetAPI tracks) and enumerates the fields returned: active domains, 24h new/deleted, ccTLD status, daily-update flag. It does not explicitly differentiate itself from the sibling tld_stats, so an agent must infer which list/stats tool to pick.

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?

States the available filters ('Filter by minimum size or ccTLD / gTLD') and that it is free, which implies bulk-enumeration usage, but gives no explicit when-to-use versus tld_stats, search_new_domains, or the other siblings, and no exclusions.

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