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

radio-browser-mcp

by cococolanosugar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

random_station

Pick and play a random internet radio station from a global database. Optionally filter by genre like jazz, rock, or news.

Instructions

Play a random station from Radio-Browser.

Args: tag: Optional genre filter (e.g. "jazz", "rock", "classical", "news"). If empty, picks from top global stations.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
tagNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.0

TDQS

A3.8/5.0
Behavior2/5

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

With no annotations, the description should disclose behavioral traits. It does not explain whether playback replaces current station, adds to queue, or just returns station info. The effect on current playback is unclear.

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 concise, with the main action in the first sentence and parameter details structured clearly. No unnecessary words.

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?

While an output schema exists, the description misses details about the effect on current playback (e.g., whether it starts streaming immediately). This is relevant given sibling tools like 'next_station' and 'stop'.

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

Parameters5/5

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

The description adds significant meaning beyond the schema: it clarifies 'tag' as a genre filter, gives examples, and explains behavior when empty. Schema coverage was 0%, so this fully compensates.

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 verb 'play' and the resource 'random station from Radio-Browser'. It distinguishes from sibling tools like 'play_station' and 'play_by_uuid' by emphasizing randomness.

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 provides when to use the tag parameter and its default behavior, but does not explicitly guide when to use this tool over siblings like 'browse_radio' or 'play_station'.

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