Mellow Mountain Radio

Chakra Guide

get_chakra_guide

Read-onlyIdempotent

Full guide to the seven chakras — Sanskrit name, Solfeggio frequency, musical note, color, element, bija mantra, petal count, governing theme, balanced and blocked states, affirmation, crystals, essential oils, yoga pose, and the Sedona vortex tied to each center.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`chakra`	No	Specific chakra — omit for all seven

Output Schema

TableJSON Schema

Name	Required	Description	Default
`note`	No
`chakras`	Yes
`chakra_sound_bath`	No
`sound_healing_page`	No

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds value by detailing the exact data returned (Sanskrit name, frequency, etc.), which helps the agent understand the output without contradicting 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, focused sentence that conveys the entire scope without waste. It could be slightly more structured, but it is effective and front-loaded with the tool's purpose.

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 that an output schema exists (per context signals), the description adequately covers all expected fields. It lists every attribute included in the guide, making it fully complete for an informational lookup tool.

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?

The single optional parameter 'chakra' is fully defined in the schema (enum, description). The tool description does not add new meaning to the parameter beyond the schema's coverage, meeting the baseline for high schema 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?

The description clearly states it is a 'Full guide to the seven chakras' and enumerates specific attributes, making the tool's purpose unmistakable. It differentiates from siblings like get_chakra_frequencies and get_solfeggio by its comprehensive scope.

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 a complete chakra reference is needed, but does not explicitly state when to avoid or compare with alternatives. The sibling list provides cues, but the description lacks direct guidance.

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?