An MCP server for King Crimson discography and live-performance history, with a curated line-up-era (incarnation) model. Aggregates record information from MusicBrainz, Discogs, Cover Art Archive, and setlist.fm.
Six tools with clear verb-noun naming (search_, get_) and reasonable descriptions (100-180 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented, LLMs cannot predict return structure. Parameters lack constraints (enums, ranges, format specs). Error handling is generic ('error' field) with no recovery guidance. No tool annotations (readOnlyHint, idempotentHint). Missing dependency hints (e.g., 'search_release returns MBID; use it with get_release_info'). Descriptions are adequate but could be more LLM-optimized per pattern:tool-description baseline (50-200 chars ideal).
Get cover art and artwork URLs for a King Crimson release by MBID from the Cover Art Archive.
Get physical editions and pressings of a King Crimson release from Discogs, including catalog numbers, formats, and market prices.
Get information about King Crimson line-up eras (incarnations), including membership, key releases, and date ranges.
Get King Crimson live performance history and setlists from setlist.fm, including tour dates, venues, and songs performed.
Get detailed information about a King Crimson release by MBID (MusicBrainz Identifier), including track listing, credits, and relationships.
Search for King Crimson releases by title or artist. Returns MBIDs (MusicBrainz Identifiers) which can be used with other tools.
Output schemas not documented. LLMs cannot predict return structure (fields, types, nesting). Baseline: 100% of A+ tools document return types.
Parameters lack constraints. 'year' in get_live_history has no range (min/max). 'incarnation_id' has no enum or format spec. Baseline: constrained inputs prevent hallucinated values.
No tool annotations (readOnlyHint, idempotentHint). All tools are read-only but this is not declared. Agents cannot distinguish safe-to-retry tools from destructive ones.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
Error handling is generic ('error' field with message). No recovery guidance. Baseline: errors should tell LLM what to do next (retry, ask user, or fatal).
No dependency hints in descriptions. LLMs don't know that search_release returns MBID needed by get_release_info, get_cover_art. Baseline: discovery tools should explain when to call them.