Skip to main content
Glama

gTLD Rankings

tld_rank
Read-onlyIdempotent

Rank TLDs by registration volume and related metrics over a chosen period.

Related: tld_trends.

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

Input Schema

NameRequiredDescriptionDefault
typeNoRanking type: 'newly' for today's new registrations, 'active' for total active domains
limitNoNumber of results (default 20, max 100)

Output Schema

NameRequiredDescriptionDefault
dataNo
dateNoData date (YYYY-MM-DD)
typeNoRanking type: 'newly' or 'active'
errorNo
totalNo
successNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • removedOutput schema / required
      Removed value: -[
      -  "success"
      -]
  2. Added

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered elsewhere. The description adds only surface context (metric being ranked) and introduces 'over a chosen period', which is unexplained and suggests temporal scoping the tool does not advertise. No annotation contradiction, but little added value.

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 short sentences, front-loaded with the action and resource, with no filler. The trailing 'Related:' fragment is terse to the point of being cryptic but still earns its space as a pointer.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With a full output schema and rich annotations, the description need not explain return values, so the bar is low and mostly met. However, the unexplained 'period' notion and the absence of any guidance on choosing between 'newly' and 'active' leave a small but real gap for a ranking 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% and both parameters (the 'newly'/'active' enum and the limit with its max) are fully documented in the schema, so the baseline applies. The description adds nothing about either parameter and its 'chosen period' phrasing could send an agent looking for a period argument that does not exist.

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 verb and resource ('Rank TLDs by registration volume'), which is enough to distinguish a leaderboard tool from siblings like tld_check or tld_trends. The qualifier 'over a chosen period' is vague and, given the schema, not obviously backed by any parameter.

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: tld_trends' points at the nearest alternative but never states the condition that selects one over the other (e.g. snapshot ranking vs. change over time). Usage is only implied by 'rank by registration volume'; there are no explicit when/when-not rules.

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.