Save edited notation
revise_scoreSave an edited MusicXML copy as the next revision of the same score; its recording, comments, panel and undo history stay. Never create a new score to change an existing one. For changes one operation cannot make: keep each exported note's id, so notes keep their timing.
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": {
"score_id": "<score_id>",
"revision": "<revision>"
},
"name": "revise_score"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| file | No | The edited MusicXML or MXL, attached. | |
| preview | No | true saves it as a suggestion the user can Apply or Discard. | |
| musicxml | No | The edited MusicXML as text, instead of file: the editing copy of this revision with every note's id kept. A note keeps its played timing whatever its written rhythm, staff or voice; a changed pitch plays the new pitch, a removed note stops sounding, a note without an id is added where it is written. Without the ids a recording's score takes only changes that keep every pitch. | |
| revision | Yes | The current saved revision, from the latest read or edit. | |
| score_id | Yes | ||
| request_id | No | A stable ID (16 to 80 letters, digits or hyphens); send the same one again after an unclear response. |