Skip to main content
Glama

KAZM Mellow Mountain Radio

by com.mellowmountainradio.mcp

Red Rock Pass Info

get_red_rock_pass
Read-onlyIdempotent

Complete Red Rock Pass guide for Sedona / Coconino National Forest — all 19 required sites, current fees, accepted passes (America the Beautiful, Senior, Access), where to buy, shuttle info, and Soldier Pass permit details. Answers the most common Sedona visitor question.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicNofees | sites | shuttles | passes | buy | all (default)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
feesNo
tipsNo
sitesNo
passesNo
shuttlesNo
kazm_noteNo
where_to_buyNo

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds value by detailing the information content (19 sites, fees, passes, etc.), which is behavioral in terms of expected output.

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?

The description is informative but slightly long, with a front-loaded first sentence that captures the essence. It could be streamlined, but each sentence adds value.

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 presence of an output schema, the description adequately covers the guide's content without needing to specify return values. It fully addresses the scope of the tool for a single-parameter, enum-driven query.

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%, so baseline is 3. The description does not add new meaning beyond the schema's enum values and description for the 'topic' parameter. The schema already defines the options succinctly.

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 it's a complete guide for the Red Rock Pass in Sedona/Coconino National Forest, listing specific topics covered (sites, fees, passes, etc.). It distinguishes itself from sibling tools like get_hiking_trails and get_jeep_trails by being uniquely about the pass.

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 implies its use for answering the most common Sedona visitor question about the pass. While it doesn't explicitly state when not to use it or mention alternatives, the context is clear enough for an agent to infer its purpose.

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