Mellow Mountain Radio

Artist Info

get_artist_info

Read-onlyIdempotent

Returns biography, genre tags, and album discography for the artist currently on KAZM, or any named artist, from MusicBrainz (open music encyclopedia).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`artist`	No	Artist name — omit to use the current now-playing artist

Output Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`tags`	Yes
`type`	Yes
`albums`	Yes
`source`	Yes
`country`	Yes
`life_span`	Yes
`searched_for`	Yes
`disambiguation`	Yes
`musicbrainz_id`	Yes

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint false. Description adds context about the data source (MusicBrainz) and output content, going beyond annotations without contradiction.

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?

Single sentence, well-structured, front-loaded with output types. No unnecessary words, 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, description sufficiently lists returned information types and data source. No missing critical details for a simple one-parameter 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?

Input schema covers the single parameter with full description. Description repeats the behavior of omitting to use current artist but adds no new semantic detail beyond schema's baseline.

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 biography, genre tags, and album discography for the current or named artist from MusicBrainz. It distinguishes from siblings like get_now_playing or get_listener_profile by specifying the resource and data type.

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?

Description implies usage for artist info but does not explicitly state when to use or when to avoid. No mention of alternatives among many sibling tools, leaving some ambiguity for the agent.

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?