Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Simplify Roll

simplify_roll

Rewrite a cymbal roll as one long tremolo note per bar, tied across barlines, to cut notation clutter while preserving the same sound.

Instructions

Rewrite a cymbal roll (a run of repeated or tied cymbal notes, e.g. a crash swell) as one long note per bar, tied across barlines, with a tremolo: the same sound with far fewer symbols. The roll starts on start_beat of start_measure (default beat 1; earlier notes in that bar stay as written) and ends at the end of end_measure, or after end_beat in it. Lengths that no single note value can hold are written as tied notes. Notes of the first chord that are not part of the roll (e.g. a kick) move to voice 2 with their own length. Refuses (changing nothing) if other notes or rests sit inside the roll or it doesn't start and end where notes do. Edits the score file and reloads it (undo with restore_backup).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "staff": "<staff>",
      "start_measure": "<start_measure>",
      "end_measure": "<end_measure>"
    },
    "name": "simplify_roll"
  }
}

Input Schema

NameRequiredDescriptionDefault
drumsNoDrums that roll, e.g. ["crash"] or ["ride"]
staffYesStaff index (0-based)
pitchesNoMIDI pitches that roll, instead of drums
slashesNoTremolo slashes (3 = a roll)
end_beatNoLast beat of the roll in end_measure, inclusive (a beat is the time signature's denominator, e.g. an eighth in 12/8, so the first two dotted quarters are end_beat=6). Defaults to the end of the bar.
score_pathNoPath of the score file. Defaults to the file of the score open in MuseScore.
start_beatNoBeat of start_measure where the roll starts (1-based, same beat unit as end_beat, so 7 is the 7th eighth in 12/8; fractions allowed). Defaults to 1.
end_measureYesBar the roll ends in
start_measureYesBar the roll starts in

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden and does so: it discloses that the score file is edited and reloaded, that undo is via restore_backup, that non-roll notes in the first chord move to voice 2 with their own length, that oversized spans become tied notes, and that it refuses without changing anything when other notes or rests intrude.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense paragraph where nearly every sentence carries new information: transformation, boundaries, tie splitting, voice 2 handling, refusal rules, and side effects. It is slightly run-on and would read better split into sentences, but there is little wasted wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a nine-parameter mutation tool with no annotations and no output schema, the description covers the mutation, its side effects, the reload, the undo path, and the exact refusal scenarios. An agent has enough to decide when to call it and what will happen.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so each of the nine parameters is already documented, and the description mostly restates start_beat defaults and end_beat/end_measure bounds. It adds some behavioral meaning (earlier notes in the start bar stay as written; beat units follow the denominator), but leaves drums, pitches, and slashes to the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource (rewrite a cymbal roll into one tied long note per bar with tremolo) and defines the input shape in musical terms (a run of repeated or tied cymbal notes, e.g. a crash swell). This is distinguishable from any general editing sibling like add_tie or add_note because it describes a specialized transformation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear qualifying conditions (the notes must form a run of repeated or tied cymbal notes, the roll must start where a note starts and end where notes end) and explicitly states the tool refuses rather than partially editing. It does not name an alternative tool for adjacent tasks, but it does point to restore_backup for undoing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools