radiobrowser-api-mcp

Overview Schema Source Related Servers Discussions Admin

get_station_by_uuid

Retrieve a specific internet radio station's details by its unique UUID. Use this action to fetch station metadata when you have a known station identifier.

Instructions

Get one station by its stationuuid (GET /json/stations/byuuid/{uuid}).

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": {
      "station_uuid": "<station_uuid>"
    },
    "name": "get_station_by_uuid"
  }
}

Input Schema

Name	Required	Description	Default
`timeout`	No
`station_uuid`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

A3.6/5.0

Behavior3/5

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

The description includes the HTTP GET method, which conveys that this is a read-only operation, and 'one station' signals the cardinality of the response. No annotations exist, so the description carries some burden, but it does not disclose error behavior, timeout semantics, or response details.

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 one concise sentence that front-loads the core operation and includes the endpoint for reference. There is no redundant or wasted wording.

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?

The tool is simple, but there is no output schema or annotations, and the description omits timeout semantics and explicit alternatives. It is minimally adequate for invoking the tool, but an agent would benefit from knowing what happens on invalid UUIDs and what the returned station object contains.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must compensate. It clarifies that station_uuid is the identifier used in the endpoint, but it does not explain the timeout parameter at all, leaving part of the behavior undocumented.

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 operation: retrieve one station by stationuuid. It is distinct from the many search/list siblings, which look up by name, country, language, etc., while this tool targets a known UUID directly.

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 the proper use case: when you already have a stationuuid and want that specific station. However, it does not explicitly state when not to use it or point to a preferred alternative for lookups without a UUID.

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