radiobrowser-api-mcp

Overview Schema Source Related Servers Discussions Admin

get_recently_updated_stations

Retrieve radio stations recently added or updated in the Radio Browser directory. Specify the number of stations and an optional timeout to get current changes.

Instructions

Most recently changed/added stations (GET /json/stations/lastchange/{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_updated_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

B3.3/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. It discloses the HTTP method (GET), implying a read-only operation, and states that stations are ordered by recent change, but it omits timeout behavior, count bounds, and any error or rate-limit behavior.

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 a single sentence containing only the essential purpose and endpoint, with no filler or redundancy. It front-loads the semantic content before the technical path, making it maximally concise.

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?

For a simple read-only list with an output schema, the description is nearly adequate: the endpoint and count placeholder cover the core invocation, and the output schema covers return shape. However, the missing timeout semantics and lack of explicit usage guidance leave notable gaps.

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 indirectly explains count via the endpoint path placeholder {count}. The timeout parameter is completely unexplained in both the schema and the description, leaving the agent to infer its meaning and units.

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 states the tool returns 'most recently changed/added stations' and provides the GET endpoint, making the resource and action identifiable. The phrase 'changed/added' distinguishes it from siblings like get_recently_clicked_stations, though it relies on the tool name for the explicit verb.

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 when to use this tool—when needing recently changed or added stations—but does not explicitly contrast it with siblings such as get_recently_clicked_stations or provide when-not-to-use guidance. The usage context is present but stated only as a noun phrase.

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