radio

List Countries

list_countries

Read-onlyIdempotent

Browse available countries with radio stations. Returns country names and station counts to help target your search geographically.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes	Total number of countries
`countries`	Yes	Countries with radio stations, sorted by station count

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedMay 24, 2026

addedInput schema / examples
```
Added value: +[
+  {}
+]
```

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of countries",
+      "type": "number"
+    },
+    "countries": {
+      "description": "Countries with radio stations, sorted by station count",
+      "items": {
+        "properties": {
+          "name": {
+            "description": "Country name",
+            "type": "string"
+          },
+          "stationcount": {
+            "description": "Number of radio stations in country",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "stationcount"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "countries"
+  ],
+  "type": "object"
+}

Changed2 schema fields changedMay 13, 2026

removedInput schema / examples

Removed value: -[
-  {
-    "_apiKey": "your-country-state-city-api-key"
-  }
-]

changedOutput schema / (root)

Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Total number of countries returned",
-      "type": "number"
-    },
-    "countries": {
-      "items": {
-        "properties": {
-          "capital": {
-            "description": "Capital city name",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "currency": {
-            "description": "Currency code",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "currency_symbol": {
-            "description": "Currency symbol",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "iso2": {
-            "description": "ISO2 country code",
-            "type": "string"
-          },
-          "iso3": {
-            "description": "ISO3 country code",
-            "type": "string"
-          },
-          "name": {
-            "description": "Country name",
-            "type": "string"
-          },
-          "phone_code": {
-            "description": "International phone code",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "region": {
-            "description": "Geographical region",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "subregion": {
-            "description": "Geographical subregion",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "required": [
-          "name",
-          "iso2",
-          "iso3",
-          "capital",
-          "phone_code",
-          "currency",
-          "currency_symbol",
-          "region",
-          "subregion"
-        ],
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "countries"
-  ],
-  "type": "object"
-}New value: +null

Changed1 schema field changedMay 8, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Total number of countries returned",
+      "type": "number"
+    },
+    "countries": {
+      "items": {
+        "properties": {
+          "capital": {
+            "description": "Capital city name",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "currency": {
+            "description": "Currency code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "currency_symbol": {
+            "description": "Currency symbol",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "iso2": {
+            "description": "ISO2 country code",
+            "type": "string"
+          },
+          "iso3": {
+            "description": "ISO3 country code",
+            "type": "string"
+          },
+          "name": {
+            "description": "Country name",
+            "type": "string"
+          },
+          "phone_code": {
+            "description": "International phone code",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "region": {
+            "description": "Geographical region",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "subregion": {
+            "description": "Geographical subregion",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "required": [
+          "name",
+          "iso2",
+          "iso3",
+          "capital",
+          "phone_code",
+          "currency",
+          "currency_symbol",
+          "region",
+          "subregion"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "countries"
+  ],
+  "type": "object"
+}

Changed1 schema field changedMay 6, 2026

addedInput schema / examples

Added value: +[
+  {
+    "_apiKey": "your-country-state-city-api-key"
+  }
+]

First observedApr 14, 2026

TDQS

A4.3/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is well covered. The description adds the return content (country names and station counts), which is useful, but does not discuss other behavioral aspects like ordering, pagination, or data freshness. Given the strong annotations, this is adequate.

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 two sentences, with the first stating the primary action and the second detailing the return value and purpose. There is zero filler, and the key information is front-loaded.

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

Completeness5/5

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

For a no-parameter, read-only listing tool with an output schema, the description fully explains what the tool does and why it is useful. It even describes the return value despite the output schema existing, which adds clarity without being redundant. No gaps are apparent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing to explain. Baseline for 0 params is 4, and the description does not attempt to artificially introduce parameter concerns. The schema coverage is trivially 100%.

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 lists countries with radio stations and returns country names and station counts. The verb 'Browse' and the resource 'available countries' make the purpose unambiguous, and it distinguishes itself from sibling tools by focusing on country-level geographic targeting.

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?

The description implies when to use this tool (to target searches geographically) but does not explicitly mention alternatives or exclusions. It gives clear context for a simple listing tool, but could be stronger by naming when not to use it (e.g., when you already know the country or need to filter stations).

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

All radio 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.

List Countries

Input Schema

Output Schema

Schema Changelog

TDQS

Glama MCP Gateway

Resources