Cloudflare Radar

Internet Quality

internet_quality

Read-onlyIdempotent

Internet Quality Index (IQI) summary — bandwidth, latency, jitter, packet loss — current value + change vs prior period. Optionally filtered to a 2-letter location code.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`location`	No	2-letter location code (e.g., "US", "DE", "JP"). Omit for global.
`date_range`	No	Lookback window: 1d \| 7d \| 14d \| 28d \| 12w \| 24w \| 52w (default 28d)

Output Schema

TableJSON Schema

Name	Required	Description
`latency`	Yes
`location`	Yes	Location code or GLOBAL
`bandwidth`	Yes
`range_end`	Yes	End time of measurement range
`date_range`	Yes	Lookback window applied
`range_start`	Yes	Start time of measurement range
`dns_resolution`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 22, 2026

addedInput schema / examples

Added value: +[
+  {
+    "date_range": "7d",
+    "location": "US"
+  },
+  {
+    "date_range": "28d"
+  }
+]

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "bandwidth": {
+      "properties": {
+        "median": {
+          "description": "50th percentile (median) value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p25": {
+          "description": "25th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p75": {
+          "description": "75th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "unit": {
+          "description": "Unit of measurement (e.g., Mbps)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "date_range": {
+      "description": "Lookback window applied",
+      "type": "string"
+    },
+    "dns_resolution": {
+      "properties": {
+        "median": {
+          "description": "50th percentile (median) value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p25": {
+          "description": "25th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p75": {
+          "description": "75th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "unit": {
+          "description": "Unit of measurement",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "latency": {
+      "properties": {
+        "median": {
+          "description": "50th percentile (median) value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p25": {
+          "description": "25th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "p75": {
+          "description": "75th percentile value",
+          "type": [
+            "number",
+            "null"
+          ]
+        },
+        "unit": {
+          "description": "Unit of measurement (e.g., ms)",
+          "type": [
+            "string",
+            "null"
+          ]
+        }
+      },
+      "type": "object"
+    },
+    "location": {
+      "description": "Location code or GLOBAL",
+      "type": "string"
+    },
+    "range_end": {
+      "description": "End time of measurement range",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "range_start": {
+      "description": "Start time of measurement range",
+      "type": [
+        "string",
+        "null"
+      ]
+    }
+  },
+  "required": [
+    "location",
+    "date_range",
+    "range_start",
+    "range_end",
+    "bandwidth",
+    "dns_resolution",
+    "latency"
+  ],
+  "type": "object"
+}

First observedMay 12, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive nature. The description adds specificity about output metrics but lacks deeper behavioral context like data source or frequency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that front-loads the purpose and key details without waste.

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 two optional parameters, high schema coverage, and an output schema, the description adequately covers the tool's purpose and output, though it could mention that it returns historical comparison data.

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% with clear descriptions for both parameters. The description restates filtering by location code but adds no new meaning beyond the schema.

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?

The description clearly states the tool provides an Internet Quality Index summary with specific metrics (bandwidth, latency, jitter, packet loss) and current value vs prior period change, clearly distinguishing it from sibling tools.

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?

The description implies usage for querying IQI data but gives no explicit guidance on when to use this tool over alternatives among siblings, nor any exclusions.

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

All Cloudflare Radar tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.