Skip to main content
Glama

Niche of One Network

Radio now

radio_now
Read-onlyIdempotent

What is on GZS 197.7 OMVFM, the Ground Zero Sum station, and where to listen.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered externally. The description adds only that the result includes a listening destination ('where to listen'); it says nothing about response shape, station scope, or whether the data is live versus cached, which is the behaviour an agent would still want to know.

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?

A single short sentence with no padding, and the station identity is front-loaded. The interrogative phrasing makes it read like a user prompt rather than a tool description, which slightly weakens the framing but costs nothing in length.

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 zero-argument, read-only lookup this is close to adequate, and the mention of 'where to listen' hints at one returned field. Because there is no output schema, the description should still say what comes back (track, artist, stream URL, etc.) and it does not, leaving the return contract underspecified.

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

Parameters4/5

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

The tool takes zero parameters (empty object, additionalProperties false), so there are no parameter semantics to explain. Baseline for a parameterless tool applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The sentence names a concrete resource (the GZS 197.7 OMVFM / Ground Zero Sum station) and an intent (what is currently airing plus where to listen), so the subject is identifiable. However it is phrased as a user question rather than a verb+resource statement, and it never distinguishes itself from near neighbours such as now_playing or radio_schedule.

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?

There is no when-to-use or when-not-to-use guidance and no alternative named. With siblings like now_playing and radio_schedule present, the agent gets no signal about which of them answers a 'currently on air' question versus a schedule or history question.

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