get_now_playingReturns the song currently on air: title, artist, album, artwork URL, start time, and stream URL.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| art | Yes | ||
| album | Yes | ||
| title | Yes | ||
| artist | Yes | ||
| elapsed_s | Yes | ||
| duration_s | Yes | ||
| started_at | Yes | ||
| stream_url | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description aligns with annotations (readOnlyHint, etc.) but adds little beyond listing returned fields. Annotations already cover safety; description doesn't disclose edge cases or absence of 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.
Is the description appropriately sized, front-loaded, and free of redundancy?
Single, efficient sentence that front-loads the key information. No wasted words.
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?
Adequately describes what the tool returns, and output schema is present. Could mention behavior when no song is playing, but not required for completeness given simplicity.
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?
No parameters in schema, so description has no burden to explain them. Baseline score of 4 is appropriate.
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?
Clearly states it returns the currently playing song with a specific list of fields (title, artist, etc.). Distinguishes from sibling tools like get_artist_info or get_rewind by specifying it's for the current track.
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?
Implies usage for current song retrieval but provides no explicit guidance on when not to use it or alternatives like get_rewind or search_song_history.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Tools are mostly distinct across categories (radio, local info, spiritual, listener management), but there is notable overlap: get_emergency_alerts and get_nws_alerts both provide alerts, and get_or_create_listener overlaps with register_listener. Also, get_chakra_frequencies, get_chakra_guide, and get_solfeggio are very similar. While descriptions help differentiate, agents may still struggle to select the right tool.
All tool names consistently use lowercase snake_case with a verb_noun pattern (e.g., get_weather, submit_song_request, log_listener_history). The verbs are predictable (get, search, submit, log, register, update) and there are no deviations like camelCase or inconsistent verb styles.
With 45 tools, the set is overgrown for a radio station server. Many tools are hyper-specific (e.g., separate tools for chakra frequencies, guide, and solfeggio; moon phase, sun times, and stargazing conditions). Consolidating similar functions would reduce cognitive load and improve coherence.
The tool set covers a broad range: radio operations, listener management, local news/weather, outdoor guides, spiritual content, etc. However, there are notable gaps: no tool to fetch full news articles (only headlines), no way to manage show schedules, and no donation or station info tools. Also, listener profile management is split across multiple tools, which feels incomplete.