radiobrowser-api-mcp

Overview Schema Source Related Servers Discussions Admin

get_most_clicked_stations

Retrieve the most-clicked internet radio stations from the Radio Browser directory. Specify a count to get a ranked list of popular stations based on user clicks.

Instructions

Most-clicked stations (GET /json/stations/topclick/{count}).

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

Input Schema

Name	Required	Description	Default
`count`	No
`timeout`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 6, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It only discloses that this is a GET endpoint, implying a read-only operation, but it does not mention response behavior, timeout handling, rate limits, or other important behavioral details.

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?

The description is a single compact sentence with no unnecessary words. It front-loads the core identifying information, though it could have added a bit more useful context without becoming verbose.

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?

For a tool with no annotations and very limited schema coverage, the description is too sparse. It omits timeout semantics, usage guidance, and behavioral context. The output schema covers return values, but the agent still lacks enough information to choose this tool correctly among many similar sibling tools.

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%, and the description only references count via the path placeholder. It does not explain what count controls beyond being in the URL, and it says nothing about timeout or their defaults despite both being defined in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly identifies the resource as 'Most-clicked stations' and gives the exact endpoint, making the purpose understandable. It doesn't explicitly contrast with siblings like get_recently_clicked_stations or get_top_voted_stations, but the meaning is still clear.

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?

There is no guidance on when to use this tool versus alternatives such as get_top_voted_stations or get_recently_clicked_stations. The description only restates the endpoint and provides no usage context, prerequisites, or exclusions.

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