Mellow Mountain Radio

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

Name	Required	Description	Default
`topic`	No	fees \| sites \| shuttles \| passes \| buy \| all (default)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`fees`	No
`tips`	No
`sites`	No
`passes`	No
`shuttles`	No
`kazm_note`	No
`where_to_buy`	No

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, making the behavioral profile clear. The description adds value by specifying that the tool is a 'complete guide' and lists content areas, enhancing transparency about what data is returned beyond the annotations.

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 a single, informative sentence that front-loads the purpose. It covers many details without excessive length, though it could be restructured for easier scanning. Slightly verbose but effective.

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 tool's simplicity (one optional parameter, annotations present, output schema exists), the description fully covers the tool's domain and purpose. Answers the most common visitor question comprehensively.

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 enum values and descriptions. The description does not add new parameter semantics beyond the schema, but it does provide context for the topics (e.g., Soldier Pass permits). 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 the tool provides a complete guide for Red Rock Pass in Sedona/Coconino National Forest, listing specific content like fees, sites, and shuttle info. It distinguishes itself from sibling tools like get_hiking_trails or get_visitor_info by focusing on a narrow, specific resource.

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 use when answering common Sedona visitor questions about Red Rock Pass, providing clear context. However, it does not explicitly state when not to use this tool or mention alternatives among siblings, leaving some ambiguity.

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

All Mellow Mountain Radio tools Inspect

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

B3.4/5.0

Disambiguation3/5

Many tools have distinct purposes, but there is overlap in areas like listener management (get_listener_profile, get_or_create_listener, register_listener, update_listener_preference, log_listener_history) and alerts (get_emergency_alerts, get_nws_alerts, get_fire_restrictions, get_wildfire_perimeters). This can cause confusion for an agent selecting the appropriate tool.

Naming Consistency3/5

Tool names mostly follow a verb_noun pattern, but verbs are inconsistent: 'get_', 'search_', 'submit_', 'log_', 'update_', 'register_', 'get_or_create_'. The listener management tools have varying verbs, and there is a mix of specific and generic names. The pattern is readable but not fully consistent.

Tool Count2/5

At 45 tools, the server is overloaded for its stated purpose as a radio station. It covers many unrelated domains (emergency alerts, hiking, chakras, etc.), which would be better split into separate, focused servers. The tool count feels excessive and unfocused.

Completeness2/5

While the radio-related tools (now playing, requests, schedule, listener management) cover core functionality, the inclusion of many unrelated tools (e.g., hiking trails, chakras, sports scores) dilutes the server's purpose. There are obvious gaps in radio-specific features (e.g., no tool for playlist management or DJ scheduling) but an overabundance of peripheral tools.

Resources

Need Help?