radiobrowser-api-mcp

Overview Schema Source Related Servers Discussions Admin

list_all_stations

Retrieve paginated lists of internet radio stations from the directory. Control page size and order to efficiently browse results.

Instructions

List stations in the directory (GET /json/stations). Paginate with offset/limit.

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": "list_all_stations"
  }
}

Input Schema

Name	Required	Default
`limit`	No
`order`	No	votes
`offset`	No
`reverse`	No
`timeout`	No
`hidebroken`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

B3.3/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral disclosure burden. It does reveal that the operation is a read-only GET and that results are paginated, which is useful. However, it does not mention default filtering behavior like hidebroken, ordering semantics, or potential large-result implications.

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?

Two short sentences with the primary action front-loaded and the pagination instruction placed immediately after. There is no filler or redundant restatement.

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

Completeness2/5

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

Even though all parameters are optional and an output schema exists, the description leaves four parameter semantics undocumented and provides no selection guidance among a large sibling set. An agent can make a default call, but cannot intentionally control ordering, timeout, or broken-station filtering.

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 only explains offset/limit via 'Paginate with offset/limit'; the other four parameters (order, reverse, timeout, hidebroken) are left entirely to inference from their names and defaults.

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 identifies the exact action ('List stations') and the target resource ('in the directory'), reinforced by the explicit endpoint GET /json/stations. This distinguishes it from search/find siblings, even though it does not name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is given on when to use this tool versus search_radio_stations, advanced_station_search, or the many find_stations_by_* alternatives. The only usage instruction is the pagination note, which addresses how to call it, not when to select it.

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