Skip to main content
Glama

KAZM Mellow Mountain Radio

by com.mellowmountainradio.mcp

Day in Music History

get_day_in_music_history
Read-onlyIdempotent

Returns notable music events that happened on this day in history — album releases, iconic concerts, chart milestones, artist birthdays — from Wikipedia's On This Day feed. Great for on-air trivia.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate as MM-DD or YYYY-MM-DD — omit for today

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
sourceYes
music_eventsYes
music_passingsYes
music_birthdaysYes

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint. The description adds value by revealing the data source (Wikipedia's On This Day feed) and providing examples of content, which aids in understanding the open-world nature.

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?

Two sentences with no unnecessary words. The first sentence delivers the core purpose, and the second adds a practical use case. Perfectly front-loaded and concise.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simple tool (one optional parameter, idempotent, read-only) and the presence of an output schema, the description adequately covers purpose, data source, and usage context without missing essential details.

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?

The single parameter 'date' has full schema description coverage (100%). The description does not add new semantics beyond the schema, only reinforcing the optional nature. Baseline score of 3 is appropriate.

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

Purpose5/5

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

The description clearly states the verb 'returns' and the resource 'notable music events on this day in history' with specific examples (album releases, concerts, chart milestones, birthdays). It distinguishes itself from siblings like get_concerts and get_events by focusing on historical music events.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description includes a usage hint ('Great for on-air trivia'), but does not explicitly state when not to use or provide alternative tools. However, the context of sibling tool names suggests its unique niche, making the usage context clear.

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

All KAZM Mellow Mountain Radio toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation3/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness3/5

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.

Resources