Skip to main content
Glama
Sign In

Static Radio

by app.staticradio
OverviewDiscussionsAdmin

What's next

whats_next
Read-onlyIdempotent

The next items coming up on one station, in airing order, with start times (UTC and US Central), shows, episode titles and links. Community bulletins in the lineup are labeled as community bulletins. To hear any of them, tune in to the station live when it airs; there is no way to play an episode on demand.

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": "<station>"
    },
    "name": "whats_next"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNoHow many upcoming items to return (1 to 20, default 5).
stationYesA station: its name (News, SHEILA B), its slug (news) or its id (news_01). See list_stations.
includeBulletinsNoInclude the community bulletins between episodes (default true).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the bar is low. The description still adds real context beyond them: results are ordered by airing time, times come in two zones, community bulletins are interleaved and labeled, and content is live-tune-only with no on-demand playback — a limitation an agent would otherwise likely hallucinate past.

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?

Three sentences, front-loaded with what is returned and in what order, followed by the bulletin labeling and the live-only caveat. Each sentence carries information, though the return-field enumeration in the first sentence is slightly packed compared to the rest.

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?

There is no output schema, so the description carries the burden of describing returns and does so adequately: items, ordering, time zones, titles and links. Combined with full schema coverage on three simple parameters and complete safety annotations, an agent has what it needs to call this correctly.

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%, so station formats, count bounds and the includeBulletins default are all already documented in the schema. The description reinforces that the call is scoped to a single station and that bulletins appear interleaved, but adds no per-parameter syntax or format detail beyond what the schema states.

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 states a concrete verb-and-resource pair ('the next items coming up on one station, in airing order') and enumerates the returned fields (start times, shows, episode titles, links), so an agent knows exactly what it fetches. It does not name any sibling, so the boundary with whats_on or find_on_now must be inferred from their own definitions.

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?

Usage is implied by the 'one station' scoping and the practical note that episodes cannot be played on demand, which steers an agent away from attempting playback. However, there is no explicit 'use this instead of X when Y' guidance and no named alternative among the sibling tools.

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

All Static Radio toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources