Skip to main content
Glama

KAZM Mellow Mountain Radio

by com.mellowmountainradio.mcp

Submit Song Request

submit_song_request

Submit a song request to KAZM 106.5 FM & 780 AM via the station website. Searches the real studio library, then logs the request for the DJ — every request gets read. Provide both song title and artist for best results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoYour name and town for the request card, e.g. 'Sarah from Sedona' (optional)
noteNoA dedication or message, e.g. 'Happy birthday Maria!' (optional)
queryYesSong title and/or artist name, e.g. 'Sailing Christopher Cross' or 'Truckin Grateful Dead'

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNo
noteNo
matchesNo
messageNo
successYes
submittedNo

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already indicate mutation (readOnlyHint=false). The description adds that the request is logged and every request gets read, going beyond the annotations. No contradictions found.

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 concise sentences, front-loaded with the action, no wasted words.

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?

Given the output schema exists and annotations cover safety, the description provides sufficient context for a simple submit tool. It could mention error handling but is adequate overall.

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?

Schema coverage is 100% with descriptions for all parameters. The description mentions providing song title and artist, but adds little beyond the schema. Baseline 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 'Submit a song request' with the specific station (KAZM 106.5 FM & 780 AM). It distinguishes from sibling 'search_song_request_library' by emphasizing submission and logging for the DJ.

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 advises 'Provide both song title and artist for best results', giving clear usage context. It does not explicitly mention when not to use or name alternatives, but the sibling tools imply this is the only submit tool.

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