Skip to main content
Glama

Niche of One Network

Listen

now_playing
Read-onlyIdempotent

What is playing now on GZS 197.7 OMVFM, the NoO Network station: track, show, up next and where to listen. Same data as radio_now.

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

Input Schema

NameRequiredDescriptionDefault
siteNoground-zero-sum

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile needs no restating. The description adds value the annotations do not: it enumerates the returned content (track, show, up next, listening options), which is important because there is no output schema. It does not mention freshness/staleness or caching, but those are minor for a lightweight read.

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?

A single sentence with no filler; the resource and its returned fields are front-loaded. Even the sibling reference is compressed to a few words rather than a paragraph.

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 one-parameter, read-only tool whose behavior is fully covered by annotations, the description supplies what the annotations cannot: the payload contents. The only gap is that the site parameter remains semantically unexplained, which is modest given its single-value enum and default.

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?

Only one parameter exists with a single-value enum ('ground-zero-sum', defaulted), and the schema carries no description of it. The description partially compensates by describing the station's branding (GZS 197.7 OMVFM, NoO Network), which plausibly maps to that site value, but it never connects the parameter to the enum or says what other sites might exist. Adequate but not compensating fully for 0% schema coverage.

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 names a concrete resource and returns: current track, current show, up next, and where to listen on a specific station (GZS 197.7 OMVFM). It also states the relationship to the sibling radio_now ("Same data as radio_now"), so an agent can recognize it as the now-playing read. It stops short of a crisp verb-first phrasing, and the equivalence claim makes the two tools' distinct roles ambiguous.

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 only implied by the name and the 'what is playing now' framing; there is no explicit statement of when to use this versus radio_history, radio_schedule, or radio_now. Saying it returns 'the same data as radio_now' identifies a sibling but gives no rule for choosing between the two, which is exactly the decision an agent needs help with.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources