lms-mcp

get_radios

Read-only

Retrieve radio directory categories and apps like TuneIn. Use a limit parameter to control the number of results.

Instructions

Get radio directory categories and apps (TuneIn, etc.)

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_radios"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	Maximum number of results (default: 100)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jun 23, 2026

TDQS

B3.2/5.0

Behavior2/5

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

Annotations already declare readOnlyHint=true, so the description's read nature is consistent but adds no additional behavioral context (e.g., pagination, ordering, side effects).

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?

Single sentence, concise and front-loaded with verb. Could be slightly more informative without verbosity, but overall efficient.

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?

No output schema exists, so description should explain return values. It mentions categories and apps but not structure. Adequate for a simple tool, but incomplete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with one parameter (limit). The description does not mention the parameter, so it adds no meaning beyond the schema. Baseline 3 per rules for high coverage.

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 clearly states the tool retrieves radio directory categories and apps, with an example (TuneIn). It uses a specific verb and resource, distinguishing it from siblings like 'get_apps' and 'get_genres'.

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 on when to use this tool versus siblings (e.g., browse_app, search_radio). The description lacks when-not-to-use and alternative suggestions.

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