Skip to main content
Glama

radio

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Search Stations

search_stations
Read-onlyIdempotent

Search radio stations by name. Returns station name, URL, country, genres, and popularity vote count. Use when looking for a specific station or browsing by keyword.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return. Defaults to 10.
queryYesStation name to search for.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
countYesNumber of stations returned
stationsYesList of radio stations matching the query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "BBC Radio 1"
+  },
+  {
+    "limit": 5,
+    "query": "jazz"
+  }
+]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stations returned",
+      "type": "number"
+    },
+    "stations": {
+      "description": "List of radio stations matching the query",
+      "items": {
+        "properties": {
+          "bitrate": {
+            "description": "Bitrate in kbps",
+            "type": "number"
+          },
+          "codec": {
+            "description": "Audio codec used",
+            "type": "string"
+          },
+          "country": {
+            "description": "Country where station broadcasts",
+            "type": "string"
+          },
+          "language": {
+            "description": "Language of broadcast",
+            "type": "string"
+          },
+          "name": {
+            "description": "Station name",
+            "type": "string"
+          },
+          "tags": {
+            "description": "Genres/tags associated with station",
+            "type": "string"
+          },
+          "url": {
+            "description": "Station stream URL (resolved or fallback)",
+            "type": "string"
+          },
+          "votes": {
+            "description": "Popularity vote count",
+            "type": "number"
+          }
+        },
+        "required": [
+          "name",
+          "url",
+          "country",
+          "language",
+          "tags",
+          "votes",
+          "codec",
+          "bitrate"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stations"
+  ],
+  "type": "object"
+}
  2. Changed2 schema fields changed
    • removedInput schema / examples
      Removed value: -[
-  {
-    "query": "Zurich HB"
-  },
-  {
-    "query": "Bern"
-  }
-]
    • changedOutput schema / (root)
      Previous value: -{
-  "properties": {
-    "count": {
-      "description": "Number of stations returned",
-      "type": "number"
-    },
-    "stations": {
-      "description": "List of matching stations",
-      "items": {
-        "properties": {
-          "coordinate": {
-            "description": "Geographic coordinates",
-            "properties": {
-              "x": {
-                "description": "X coordinate (longitude)",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              },
-              "y": {
-                "description": "Y coordinate (latitude)",
-                "type": [
-                  "number",
-                  "null"
-                ]
-              }
-            },
-            "type": [
-              "object",
-              "null"
-            ]
-          },
-          "id": {
-            "description": "Station identifier",
-            "type": [
-              "string",
-              "null"
-            ]
-          },
-          "name": {
-            "description": "Station name",
-            "type": [
-              "string",
-              "null"
-            ]
-          }
-        },
-        "type": "object"
-      },
-      "type": "array"
-    }
-  },
-  "required": [
-    "count",
-    "stations"
-  ],
-  "type": "object"
-}New value: +null
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "count": {
+      "description": "Number of stations returned",
+      "type": "number"
+    },
+    "stations": {
+      "description": "List of matching stations",
+      "items": {
+        "properties": {
+          "coordinate": {
+            "description": "Geographic coordinates",
+            "properties": {
+              "x": {
+                "description": "X coordinate (longitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              },
+              "y": {
+                "description": "Y coordinate (latitude)",
+                "type": [
+                  "number",
+                  "null"
+                ]
+              }
+            },
+            "type": [
+              "object",
+              "null"
+            ]
+          },
+          "id": {
+            "description": "Station identifier",
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "name": {
+            "description": "Station name",
+            "type": [
+              "string",
+              "null"
+            ]
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "count",
+    "stations"
+  ],
+  "type": "object"
+}
  4. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "Zurich HB"
+  },
+  {
+    "query": "Bern"
+  }
+]
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the read-only nature is known. The description adds value by disclosing the returned data structure (station name, URL, country, genres, popularity vote count) and that it accepts a keyword for browsing. No contradiction with annotations; the description complements them with functional detail.

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 three concise sentences, each serving a distinct purpose: core action, return values, and usage guidance. It is front-loaded with the key action and contains no redundant or filler words.

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?

Given the tool's simplicity (2 parameters, 1 required), the available annotations, and an output schema, the description is fully adequate. It covers the action, return values, and usage context. Although an output schema exists, the description's mention of return values is a harmless supplement, and no critical behavioral details are missing.

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%: both 'query' and 'limit' have meaningful descriptions, so the baseline is 3. The description text does not add further parameter semantics beyond what the schema provides, such as default values or type details, so it neither improves nor worsens clarity.

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 opens with 'Search radio stations by name', which clearly states the action (search) and the resource (radio stations). It also specifies the output fields (name, URL, country, genres, popularity vote count), making the tool's scope unambiguous. This distinguishes it from sibling tools like get_top_stations or search_within by emphasizing name-based lookup.

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 explicitly states 'Use when looking for a specific station or browsing by keyword', providing clear context for when to invoke this tool. However, it does not mention 'when not to use' or name alternative tools, so it stops short of full exclusion guidance.

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

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

Resources