Skip to main content
Glama
Sign In
radio-browser-mcp

radio-browser-mcp

by cococolanosugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

play_station

Find and play internet radio stations by name. Supports partial name matching for quick access to thousands of stations worldwide.

Instructions

Play a station by name from Radio-Browser global directory. Partial name matching is supported (case-insensitive).

Args: name: Station name (e.g. "BBC Radio 1", "jazz fm")

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "play_station"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations provided; description only says 'Play' without detailing side effects (e.g., stopping current playback) or return behavior. Partial matching info is useful but thin.

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 sentences plus an Args section are concise. The Args section is slightly redundant but adds an example without unnecessary length.

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?

Given the simple tool and presence of output schema, the description covers the basic action. However, it lacks context on playback behavior (e.g., queueing vs streaming).

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?

The 'name' parameter is explained with examples but the schema itself has 0% description coverage. Description adds value but is minimal.

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 'Play a station by name' with a specific verb and resource. It distinguishes from siblings like play_by_uuid by specifying name matching.

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?

Mentions partial name matching and case-insensitivity, but does not explicitly state when to use this tool over alternatives like play_by_uuid or browse_radio.

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

Deploy Server

Other Tools