ScoreStarling

Create score from notation

create_score

Make a new score from notation you write (ABC or MusicXML) or a file you wrote: an arrangement the user asks for, music read from frames, or music they type. No credits; it returns its panel. Fixes to an existing score go into it. From an existing score, pass source_score_id to keep its recording.

Input Schema

Name	Required	Description	Default
`bpm`	No	Playback tempo, overriding the notation's own.
`file`	No	A MusicXML, MXL or ABC file you wrote, instead of notation.
`view`	No	staff, jianpu (1 = the key, movable do), jianpu_fixed (1 = C, fixed do) or jianpu_melody (top line only).
`title`	No	Named after its version, such as "My song (easy)".
`format`	No	abc or musicxml.	abc
`notation`	No	ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a "Swing" or "Shuffle" word (ABC Q:"Swing" 1/4=110, or "^Swing" on a note), and playback swings the eighths of every part 2:1 from there until a "Straight" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Playback follows repeat signs; at most 30 minutes.
`source_score_id`	No	The score it derives from: inherits its audio or video by default, without asking; check the alignment before claiming it plays in sync.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 25, 2026

changedInput schema / properties / notation / description

Previous value: -"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Playback follows repeat signs; at most ten minutes."New value: +"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Playback follows repeat signs; at most 30 minutes."

Changed2 schema fields changedOct 25, 2026

changedInput schema / properties / notation / description

Previous value: -"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Repeats play once as written; at most ten minutes."New value: +"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Playback follows repeat signs; at most ten minutes."

changedInput schema / properties / title / description

Previous value: -"Named after its version, such as \"Für Elise (easy)\"."New value: +"Named after its version, such as \"My song (easy)\"."

Changed28 schema fields changedOct 24, 2026

removedInput schema / properties / bpm / anyOf

Removed value: -[
-  {
-    "type": "number"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / bpm / default
```
Removed value: -null
```

addedInput schema / properties / bpm / description

Added value: +"Playback tempo, overriding the notation's own."

addedInput schema / properties / bpm / type
```
Added value: +"number"
```
addedInput schema / properties / file / additionalProperties
```
Added value: +false
```

removedInput schema / properties / file / anyOf

Removed value: -[
-  {
-    "additionalProperties": false,
-    "properties": {
-      "download_url": {
-        "type": "string"
-      },
-      "file_id": {
-        "type": "string"
-      },
-      "file_name": {
-        "default": "",
-        "type": "string"
-      },
-      "mime_type": {
-        "default": "",
-        "type": "string"
-      }
-    },
-    "required": [
-      "download_url",
-      "file_id"
-    ],
-    "type": "object"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / file / default
```
Removed value: -null
```

addedInput schema / properties / file / description

Added value: +"A MusicXML, MXL or ABC file you wrote, instead of notation."

addedInput schema / properties / file / properties

Added value: +{
+  "download_url": {
+    "type": "string"
+  },
+  "file_id": {
+    "type": "string"
+  },
+  "file_name": {
+    "default": "",
+    "type": "string"
+  },
+  "mime_type": {
+    "default": "",
+    "type": "string"
+  }
+}

addedInput schema / properties / file / required

Added value: +[
+  "download_url",
+  "file_id"
+]

addedInput schema / properties / file / type
```
Added value: +"object"
```
addedInput schema / properties / format / description
```
Added value: +"abc or musicxml."
```

removedInput schema / properties / notation / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / notation / default
```
Removed value: -null
```

changedInput schema / properties / notation / description

Previous value: -"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word."New value: +"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word. Several parts and staves, chord symbols and lyrics; ABC headers X, T, M, L, Q (the written tempo) and K. Repeats play once as written; at most ten minutes."

addedInput schema / properties / notation / type
```
Added value: +"string"
```

removedInput schema / properties / source_score_id / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / source_score_id / default
```
Removed value: -null
```

addedInput schema / properties / source_score_id / description

Added value: +"The score it derives from: inherits its audio or video by default, without asking; check the alignment before claiming it plays in sync."

addedInput schema / properties / source_score_id / type
```
Added value: +"string"
```

removedInput schema / properties / title / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / title / default
```
Removed value: -null
```

addedInput schema / properties / title / description

Added value: +"Named after its version, such as \"Für Elise (easy)\"."

addedInput schema / properties / title / type
```
Added value: +"string"
```

removedInput schema / properties / view / anyOf

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

removedInput schema / properties / view / default
```
Removed value: -null
```

addedInput schema / properties / view / description

Added value: +"staff, jianpu (1 = the key, movable do), jianpu_fixed (1 = C, fixed do) or jianpu_melody (top line only)."

addedInput schema / properties / view / type
```
Added value: +"string"
```

Changed1 schema field changedOct 22, 2026

addedInput schema / properties / notation / description

Added value: +"ABC or MusicXML text. Every bar must fit its time signature (count L: units); a score whose bars hold more is refused unsaved. A style is more than chords and sound: write its rhythm and melody (a blues or rock line, a walking bass, fills). Swing or shuffle: write even eighths under a \"Swing\" or \"Shuffle\" word (ABC Q:\"Swing\" 1/4=110, or \"^Swing\" on a note), and playback swings the eighths of every part 2:1 from there until a \"Straight\" word."

Changed1 schema field changedOct 17, 2026

addedInput schema / properties / source_score_id

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Changed5 schema fields changedOct 8, 2026

addedInput schema / properties / file

Added value: +{
+  "anyOf": [
+    {
+      "additionalProperties": false,
+      "properties": {
+        "download_url": {
+          "type": "string"
+        },
+        "file_id": {
+          "type": "string"
+        },
+        "file_name": {
+          "default": "",
+          "type": "string"
+        },
+        "mime_type": {
+          "default": "",
+          "type": "string"
+        }
+      },
+      "required": [
+        "download_url",
+        "file_id"
+      ],
+      "type": "object"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / notation / anyOf

Added value: +[
+  {
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / notation / default
```
Added value: +null
```
removedInput schema / properties / notation / type
```
Removed value: -"string"
```
removedInput schema / required
```
Removed value: -[
-  "notation"
-]
```

First observedOct 8, 2026

TDQS

A3.9/5.0

Behavior5/5

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

Goes well beyond the annotations: discloses that there are no credits consumed, that it returns its panel, that malformed bars are 'refused unsaved', that playback follows repeats, that scores are capped at 30 minutes, and that a source score's recording is inherited silently so alignment must be checked before claiming sync. This is the kind of operational detail an agent needs and cannot get from the schema.

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?

Short and front-loaded with the core action and input modes, and most sentences carry real content. The parenthetical list of origins ('an arrangement the user asks for, music read from frames, or music they type') is somewhat redundant and the 'Fixes to an existing score go into it' clause is ambiguous enough to cost clarity.

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

Completeness4/5

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

For a 7-parameter creation tool with no output schema, the description covers cost, the returned panel, validation failure behavior, duration limits, and the derivation caveat, which is nearly everything an agent needs. Remaining gaps (how title/view should be chosen, what 'refused unsaved' means for retry) are minor since the schema documents those fields.

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 description coverage is 100%, so the schema already explains each parameter including source_score_id's inheritance and the notation constraints. The description largely overlaps that ground (repeating the source_score_id inheritance and notation format notes) rather than adding syntax or precedence rules, so baseline 3 applies.

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

Purpose4/5

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

States a specific verb and resource ('Make a new score from notation... or a file') and enumerates the input modes, which tells an agent what it produces. It does not clearly name the sibling it differs from (edit_score/revise_score), and the sentence 'Fixes to an existing score go into it' muddies whether it is the mutation path for corrections.

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

Usage Guidelines3/5

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

Usage conditions are implied by the enumeration ('an arrangement the user asks for, music read from frames, or music they type') and the source_score_id note for deriving from an existing score, but there are no explicit when-not rules or named alternatives such as edit_score or save_score_edits for revisions, which is exactly where an agent is most likely to misroute.

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

All ScoreStarling tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?