get_now_playingRetrieve the current live track, stream URL, and station status from Lightning FM's on-air activity feed.
Read the current live activity (NIP-53, kind 30311) Lightning FM publishes on every track change: the track currently on air, the stream URL, and station status.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.5Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It clearly labels the operation as a read, exposes the live/NIP-53 protocol detail, and states what information is returned. It does not mention failure modes, latency, or auth, but for a zero-parameter public read that is a minor gap.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single tight sentence that front-loads the verb and resource, then adds protocol and return details. Every clause earns its place with no repetition or fluff.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter read with no output schema, the description needs to explain what the tool returns and does, and it does so concretely (track, stream URL, station status). It could slightly improve by noting what happens when no track is currently on air, but the station status detail partially covers that.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool takes zero parameters, so the schema holds no parameter information for the description to enhance. According to the baseline for zero-parameter tools, this is a Strong case: nothing is missing.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description names a specific verb ('Read'), a specific resource ('current live activity ... Lightning FM publishes'), and the exact data elements returned (track, stream URL, station status). It clearly distinguishes this from sibling search-oriented tools like search_catalog and get_artist by focusing on live, current state rather than catalog lookup.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description says it reads current live activity and the track currently on air, which gives clear context for when to use it. It does not explicitly name sibling alternatives or say when not to use it, but the 'current' vs. search distinction is strong enough that an agent should route correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.