MCP server for LLM-driven retro chiptune-style MML composition
Single tool 'compose_mml' has a well-structured schema with 6 parameters, all typed and described. Tool description is clear (95 chars) and explains the three actions. However, output schema is not formally documented in the tool definition, the code shows internal ToolExecution dataclass but no explicit return schema declaration visible to the MCP client. Parameter descriptions are adequate but lack constraint details (e.g., no explicit enum for 'action' or 'mode' in the schema, though code validates them). Error handling returns structured validation objects but lacks recovery guidance. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) present.
Compose, validate, or retrieve MML templates for chiptune music synthesis
Output schema not formally documented. Tool returns ToolExecution with nested dicts (success, audio, duration_sec, validation, etc.) but no explicit JSON Schema definition visible in tool registration. LLMs cannot plan downstream operations without knowing return structure.
Parameter 'action' accepts 'compose', 'validate', 'template' but is not declared as an enum in the schema, only as a free-form string with description. LLMs may hallucinate invalid actions.
Parameter 'mode' similarly lacks enum constraint in schema (should be ['ppmck', 'pyxel']). Code validates but schema does not enforce.
Error responses include structured validation objects but lack recovery guidance. E.g., 'mml and mode are required' does not suggest 'call template action first to see examples'.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
No tool annotations present. 'compose' action modifies state (writes WAV files to disk) but is not marked with destructiveHint. 'validate' and 'template' are read-only but lack readOnlyHint.