fix: remove stale sequence_viewer / wrong viewer_type examples in MCP surface
musehub#117 wrap-up audit found DOM_05/DOM_09's viewer_type enum change (generic/symbol_graph/piano_roll, dropping the never-implemented sequence_viewer) was applied to the REST schema and CLI docs (DOM_14) but never to the MCP tool surface, which several agents use as their primary interface:
- MusehubDomain model's inline comment still listed sequence_viewer as a valid value, contradicting the Literal enum enforced server-side. - mcp/resources.py's "protocol" resource content (fetched by agents to learn the capabilities schema) also listed sequence_viewer. - mcp/tools/musehub.py's musehub_publish_domain tool: description and per-field schema wrongly nested viewer_type inside "capabilities" (it is a sibling top-level parameter), claimed capabilities keys were required (all are optional, matching DOM_06), and gave invalid example values ('midi', 'code', 'spatial', 'genome', 'sequence') for viewer_type — an agent copy-pasting the worked example would get a real 422. - musehub_list_domains's viewer_type filter description also listed an invalid example ('code_graph' instead of 'symbol_graph').
No test pinned these description strings; 181/181 MCP tests still pass.
Semantic Changes
3 symbols
Files Changed
~3
1003 in snapshot
0 comments
muse hub commit comment sha256:bfe83e6be26ccb9017794f6aec65e3c9db5abf92edc33a5e07b32042a486a345 --body "your comment"
No comments yet. Be the first to start the discussion.