Skip to main content
Glama

KAZM Mellow Mountain Radio

by com.mellowmountainradio.mcp

Stargazing Conditions

get_stargazing_conditions
Read-onlyIdempotent

Returns tonight's stargazing forecast for Sedona, AZ — astronomical darkness window, moon interference, Milky Way galactic core visibility, and best times to shoot the night sky. Sedona sits near the Verde Valley Dark Sky corridor.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateNoDate YYYY-MM-DD (default tonight)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
moonYes
sourceYes
darknessYes
locationYes
milky_wayYes
top_sitesYes

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, destructiveHint. Description adds meaningful behavioral context (Sedona's dark sky corridor, specific forecast components) without contradicting annotations. No mention of side effects or auth, but annotations cover safety.

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, first sentence front-loaded with main action and key outputs, second adds location context. No unnecessary words.

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?

For a tool with one optional parameter and output schema, description sufficiently lists key return elements (astronomical darkness, moon interference, Milky Way visibility, best times). No gaps for intended use.

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?

Only one parameter (date) with 100% schema coverage. Description mentions default 'tonight' but adds no new meaning beyond schema. Baseline 3 for high coverage.

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?

Description clearly states it returns a stargazing forecast for Sedona, with specific elements like astronomical darkness, moon interference, Milky Way visibility. Distinguishes from siblings like get_moon_phase or get_sun_times by focusing on night sky photography conditions.

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

Usage Guidelines3/5

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

Implied usage for stargazing in Sedona, but no explicit guidance on when to use this tool vs alternatives like get_moon_phase or get_weather. No when-not-to-use or prerequisites mentioned.

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