Loading ToolBench
Control GrandOrgue pipe organ: MIDI bridge, stops, pistons, manuals, sample sets
GrandOrgue MCP has 7 tools with basic schemas and descriptions, but significant gaps limit production readiness. All tools have descriptions (10-80 chars, mostly adequate) and input schemas with type definitions. However, parameter descriptions are sparse or missing entirely. Output schemas are undocumented, LLMs cannot predict return structure. Error handling is absent; no guidance on retryability, user-fixable vs fatal errors, or recovery paths. Tool naming follows verb_noun convention (go_*, midi_depot_*) but lacks clarity on side effects. No pagination support despite file operations. Security concerns: midi_depot_upload/delete expose file operations without documented permission checks or rate limiting.
Load a GrandOrgue organ by path or name. Auto-loads if available.
Get GrandOrgue process, MIDI, and organ status.
Download and extract MIDI files from the Bach Central bundle.
Delete a MIDI file from the depot.
Download a MIDI file from the depot (returns base64 encoded).
List all MIDI files in the depot directory.
Upload a MIDI file to the depot (base64 encoded).
Output schemas completely undocumented. LLMs cannot predict what fields go_status, midi_depot_list, or midi_depot_download return. This forces agents to guess structure and wastes tokens on trial-and-error parsing.
Parameter descriptions missing or trivial. 'path' in go_load_organ lacks format guidance (is it absolute? relative? .organ extension required?). 'data_base64' in midi_depot_upload has no size limits, encoding validation, or error cases documented.
No error handling guidance. Tools lack recovery hints. If midi_depot_upload fails (disk full, invalid base64, name collision), LLM receives no actionable error message or retry strategy. No distinction between retryable and fatal errors.
Inferred effective spec: <=2025-11-25.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 55 | <=2025-11-25 | v2 |
Destructive operations (midi_depot_delete, midi_depot_bach) lack confirmation or dry-run support. Agents can permanently delete MIDI files or overwrite depot without safeguards. No audit trail or undo mechanism documented.
No pagination or result limits documented. midi_depot_list could return thousands of files, exhausting context. No limit parameter, no cursor/offset, no total count in response structure.