No user-submitted related servers found.
Scored across 7 tools
The read tools have a clear subset relationship (get_score_metadata is a lighter get_score) and connect/ping are distinguishable, but two generic escape hatches exist: processSequence runs documented actions while run_qml runs arbitrary code that can itself call ctx.processCommand, so their boundary is fuzzy. Descriptions help, but an agent must reason about which execution path to pick.
Six of seven tools follow a consistent snake_case verb_noun pattern (connect_to_musescore, get_score, get_cursor_info, run_qml, etc.). processSequence is the sole camelCase outlier, a minor but noticeable deviation from an otherwise predictable convention.
Seven tools is well within the sweet spot and the set is logically grouped (connection, reads, execution). The one arguable redundancy is get_score_metadata, whose output is already contained in get_score, so not every tool strictly earns its place.
Connection, health/version check, full and partial score reads, cursor/selection state, batched action sequencing, and arbitrary scripting give broad lifecycle coverage, including edits and rollback. Gaps are minor: no explicit disconnect/close tool and no tool to enumerate available actions (agents must consult docs/ACTIONS.md externally).