radiobrowser-api-mcp

Overview Schema Source Related Servers Discussions Admin

get_recently_clicked_stations

Returns radio stations most recently clicked by Radio Browser users, ordered by click time. Specify a count to limit results, enabling discovery of currently active stations.

Instructions

Most recently clicked stations (GET /json/stations/lastclick/{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_recently_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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals the HTTP method GET and the notion of recency, but does not explain ordering, recency window, click-source semantics, or whether the operation is read-only in any explicit way.

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 sentence with no fluff and the endpoint is front-loaded. It is appropriately short, though it sacrifices useful detail for brevity.

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?

With no annotations, zero schema description coverage, and no usage guidance, the description is under-specified for reliable invocation. The presence of an output schema does not compensate for missing parameter semantics and behavioral context.

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 for the missing parameter documentation. It gives partial meaning to 'count' via the endpoint path, but does not explain valid ranges, default behavior, or the 'timeout' parameter at all.

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 and operation: most recently clicked stations, backed by the GET endpoint. It does not explicitly distinguish itself from get_most_clicked_stations, but the word 'recently' provides some differentiation.

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 provided about when to use this tool versus get_most_clicked_stations, get_recently_updated_stations, or register_station_click. The description leaves selection entirely to inference.

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