Skip to main content
Glama

Save edited notation

revise_score

Save an edited copy of an existing score as the next revision of the SAME score: its recording, playback comparison, comments, open panel and undo history stay. Never create a new score to change an existing one. Use it for any change a single score edit cannot make, such as moving notes between staves, hands or voices, deleting a misheard voice, correcting many pitches, adding notes, rhythm spelling, ties, beams or marks: export this revision as MusicXML, edit that file keeping each note's id attribute, and pass it as file (a MusicXML or MXL attachment) or as musicxml text. A note keeps its played timing whatever its written rhythm, staff or voice; a changed pitch plays at the new pitch, a removed note stops sounding, and a note without an existing id is added to the playing where it is written (inside the recording's length). Parts stay the same. Without the exported IDs, a recording's score accepts only notation changes that keep every pitch; a score made from written music plays the file as written. preview=true creates a suggestion for the user to Apply or Discard.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fileNo
previewNo
musicxmlNo
revisionYes
score_idYes
request_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

Score is being calculated.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources