Mellow Mountain Radio

Personalized Content

get_personalized_content

Read-onlyIdempotent

Returns a fully personalized KAZM experience — greeting in the listener's language, recommendations from their history, station brief. Accepts listener_id OR email, so no separate registration step is ever needed. Pairs perfectly with get_or_create_listener.

Input Schema

TableJSON Schema

Name	Required	Description
`email`	No	Email address — alternative to listener_id
`listener_id`	No	The listener's unique ID
`content_type`	No	greeting = localized welcome only; recommendations = based on history; full = everything (default)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`greeting`	No
`listener`	Yes
`session_tip`	No
`recommendations`	No

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already show read-only, idempotent, non-destructive. Description adds concrete behavior (returns greeting, recommendations, etc.) and input flexibility, no contradictions.

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, front-loaded with result, no waste. Highly efficient.

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 output schema exists and annotations cover safety, description is complete—covers what it returns, how to call, and companion tool.

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 coverage is 100%. Description adds value by explaining the OR relationship for listener_id/email and the effect of content_type beyond enum labels.

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 the tool returns a fully personalized KAZM experience with specific components (greeting, recommendations, station brief). Distinct from many get_* siblings.

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?

Specifies it accepts listener_id OR email and pairs perfectly with get_or_create_listener, giving clear context. Lacks explicit when-not-to-use, but sufficient.

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?