Skip to main content
Glama

Radar Domain Rank

radar_domain_rank
Read-onlyIdempotent

Is this domain widely visited, or nowhere? Returns a single domain's Cloudflare Radar popularity: an exact rank for domains inside the global top 100, otherwise only a bucket (e.g. "200" = top 200, "100000" = top 100k), rank is null for everything outside the top 100, so do not build logic on it populating. Below Radar's tracked ceiling (bucket ">200000") there is NO signal at all: Radar does not verify domain existence, so a real-but-obscure site and a domain that has never existed come back identically. Read ranked and interpretation, not just bucket, to tell those apart.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "domain": "reddit.com"
    },
    "name": "radar_domain_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
dateNoISO date (YYYY-MM-DD) for a historical ranking snapshot. Omit for the latest.
domainYesDomain to look up, e.g. "reddit.com" (no scheme/path).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior5/5

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

Goes well beyond the readOnly/idempotent/openWorld annotations: discloses that `rank` is null outside the top 100, the bucket encoding ("200" = top 200), the absence of signal beyond bucket ">200000", and that Radar does not verify domain existence so obscure-real and nonexistent domains look identical. This is exactly the behavioral context an agent needs to avoid misinterpreting results.

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-loads the purpose as a question, then layers the rank/bucket mechanics and the key caveat in a logical order. It is dense but nearly every clause carries real information; only the rhetorical opener is slightly stylistic 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?

With no output schema, the description must explain return values, and it does cover `rank`, `bucket`, `ranked`, and `interpretation`. It never specifies the type or meaning of `ranked`/`interpretation` beyond 'read them to tell cases apart', leaving a modest gap for a tool whose output is entirely described in prose.

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 coverage is 100% and both parameters are documented in the schema, including the no-scheme/path constraint and the historical `date` option. The description adds no further parameter meaning and does not mention the `date` snapshot behavior, so the baseline 3 applies.

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 a specific verb and resource: returns a single domain's Cloudflare Radar popularity rank/bucket. The opening question frames the exact decision the tool answers, and it is clearly distinct from list-style siblings such as radar_top_domains.

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?

Gives strong context on when the result is meaningful and explicitly warns not to build logic on `rank` populating outside the top 100. It stops short of naming an alternative tool or stating an explicit when-not-to-call condition (e.g. for bulk lookups), so it is clear but not fully routing.

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.