Mellow Mountain Radio

Sunrise & Sunset Times

get_sun_times

Read-onlyIdempotent

Returns sunrise, sunset, solar noon, day length, golden hours, and astronomical twilight for Sedona from the KAZM transmitter site. Optional date param for any day. Also flags next solstice and equinox.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`date`	No	Date in YYYY-MM-DD format — omit for today

Output Schema

TableJSON Schema

Name	Required	Description	Default
`date`	Yes
`source`	Yes
`sunset`	Yes
`sunrise`	Yes
`location`	Yes
`solar_noon`	Yes
`civil_twilight_end`	Yes
`day_length_seconds`	Yes
`civil_twilight_begin`	Yes
`nautical_twilight_end`	Yes
`nautical_twilight_begin`	Yes
`next_solstice_or_equinox`	No
`astronomical_twilight_end`	Yes
`astronomical_twilight_begin`	Yes

TDQS

A4.5/5.0

Behavior4/5

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

Annotations indicate read-only, idempotent, non-destructive. Description adds specific return fields and the solstice/equinox flag, exceeding basic transparency.

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, no wasted words, front-loaded with essential information.

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?

Output schema likely defines return structure; description lists key return fields, making it complete for the tool's purpose.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers 100% of parameters. Description adds meaning by explaining the date parameter is optional and can be omitted for today, which is not in the schema.

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?

Clearly states the tool returns specific solar times (sunrise, sunset, etc.) for a defined location (Sedona from KAZM transmitter), distinguishing it from siblings like get_moon_phase or get_stargazing_conditions.

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?

Mentions optional date parameter for any day, implying usage context. Could explicitly exclude other locations but the description is clear enough.

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?