Skip to main content
Glama
Sign In
radiobrowser-api-mcp

radiobrowser-api-mcp

by maxim75
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

register_station_click

Record a station listen by registering a click, incrementing its public counter and returning the station record.

Instructions

Register a click (listen) for a station (GET /json/click/{uuid}).

NOTE: increments the station's public click counter. Returns the station record.

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

Input Schema

NameRequiredDescriptionDefault
timeoutNo
station_uuidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations present, the description carries the disclosure burden and does disclose a key side effect: 'increments the station's public click counter'. It also states the return value. It omits edge cases like auth/rate limits, but the main behavioral trait is explicit.

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 no wasted text; the primary action is front-loaded and the side-effect note is placed where it cannot be missed.

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

Completeness4/5

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

For a simple two-parameter tool with no output schema, the description provides the essential behavior, side effect, and return value. It doesn't cover error behavior, but the complexity is low enough that this is a minor gap.

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 identifies the station via the endpoint '{uuid}', which maps to station_uuid, but it never explains the timeout parameter. Thus only half the parameters receive added meaning.

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?

States a specific action and resource: 'Register a click (listen) for a station', and even ties it to the exact endpoint. This makes it clearly distinct from the many search/list sibling tools.

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

Usage Guidelines4/5

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

Clear context is given: use it to record a click/listen and it will increment the station's public counter. It does not explicitly name alternatives or say when not to use it, but the mutation-like behavior is self-evident against the read-oriented sibling tools.

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

Deploy Server

Other Tools