ScoreStarling

Transcribe again

transcribe_again

Transcribe a score's original recording again as a new score; the original stays. Only when the user asks for a new transcription, never merely to fix notation. It can use credits again: without credits and consent=true it returns needs_confirmation and creates nothing.

Input Schema

Name	Required	Description	Default
`view`	No	staff, jianpu (1 = the key, movable do), jianpu_fixed (1 = C, fixed do) or jianpu_melody (top line only). The original's by default.
`consent`	No	true only after the user approved those credits.
`credits`	No	The credits the user approved, as needs_confirmation reported them.
`preview`	No	true: a free 30-second preview instead of the whole piece, only when the user asks to try one first.
`provider`	No	local (one instrument or voice), piano (solo piano) or mirelo (a band: uses credits, priced first).	local
`score_id`	Yes	The finished or stopped score whose recording is used.
`pro_options`	No	Band (Pro) rhythm and paper choices, each optional: only user-supplied or source-established ones. Pass a source-established time_signature: omission uses N/4 and never detects 6/8, 9/8 or 12/8. Otherwise timing performance (quantized snaps to a reliable beat), subdivision found by Pro, tempo follow (fixed: one tempo, at bpm), page_size a4.
`replay_only`	No	Test accounts only: reuse an exact saved band result, never new processing.
`review_instruments`	No	Band only: true (default) holds it for the instrument list before the price.

Schema Changelog

Changes observed during successful MCP inspections.

Changed21 schema fields changedOct 24, 2026

removedInput schema / $defs

Removed value: -{
-  "ProOptions": {
-    "additionalProperties": false,
-    "description": "Pro (Mirelo) rhythm and paper choices; each one left out keeps its default.",
-    "properties": {
-      "bpm": {
-        "anyOf": [
-          {
-            "maximum": 300,
-            "minimum": 30,
-            "type": "number"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "The constant tempo for tempo fixed, sent to Pro as given; the result states the tempo written (time_grid.tempo_bpm)."
-      },
-      "page_size": {
-        "anyOf": [
-          {
-            "enum": [
-              "a4",
-              "letter"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Paper of the supplier PDFs and MusicXML; a4 (default) or letter."
-      },
-      "subdivision": {
-        "anyOf": [
-          {
-            "enum": [
-              "automatic",
-              "straight_sixteenths",
-              "eighth_triplets",
-              "sixteenth_triplets",
-              "swing_eighths"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Rhythmic grid. Omit it to let Pro choose; it keeps straight sixteenths unless triplets are clear."
-      },
-      "tempo": {
-        "anyOf": [
-          {
-            "enum": [
-              "follow",
-              "fixed"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "follow (default) keeps the tempo changes of the playing; fixed writes one constant tempo, at bpm or else at the tempo Pro detects. A bpm given with the upload means fixed."
-      },
-      "time_signature": {
-        "anyOf": [
-          {
-            "enum": [
-              "2/4",
-              "3/4",
-              "4/4",
-              "5/4",
-              "6/4",
-              "7/4",
-              "9/4",
-              "12/4",
-              "6/8",
-              "9/8",
-              "12/8"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Omit it to let Pro find the meter (written as N/4); choose 6/8, 9/8 or 12/8 explicitly for a compound meter."
-      },
-      "timing": {
-        "anyOf": [
-          {
-            "enum": [
-              "performance",
-              "quantized"
-            ],
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "performance (default) keeps the played timing; quantized aligns notes to the beat when Pro finds a reliable beat grid, otherwise the result reports a fallback."
-      }
-    },
-    "type": "object"
-  }
-}

addedInput schema / properties / consent / description

Added value: +"true only after the user approved those credits."

removedInput schema / properties / credits / anyOf

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

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

addedInput schema / properties / credits / description

Added value: +"The credits the user approved, as needs_confirmation reported them."

addedInput schema / properties / credits / type
```
Added value: +"integer"
```

addedInput schema / properties / preview / description

Added value: +"true: a free 30-second preview instead of the whole piece, only when the user asks to try one first."

addedInput schema / properties / pro_options / additionalProperties
```
Added value: +false
```

removedInput schema / properties / pro_options / anyOf

Removed value: -[
-  {
-    "$ref": "#/$defs/ProOptions"
-  },
-  {
-    "type": "null"
-  }
-]

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

addedInput schema / properties / pro_options / description

Added value: +"Band (Pro) rhythm and paper choices, each optional: only user-supplied or source-established ones. Pass a source-established time_signature: omission uses N/4 and never detects 6/8, 9/8 or 12/8. Otherwise timing performance (quantized snaps to a reliable beat), subdivision found by Pro, tempo follow (fixed: one tempo, at bpm), page_size a4."

addedInput schema / properties / pro_options / properties

Added value: +{
+  "bpm": {
+    "maximum": 300,
+    "minimum": 30,
+    "type": "number"
+  },
+  "page_size": {
+    "enum": [
+      "a4",
+      "letter"
+    ],
+    "type": "string"
+  },
+  "subdivision": {
+    "enum": [
+      "automatic",
+      "straight_sixteenths",
+      "eighth_triplets",
+      "sixteenth_triplets",
+      "swing_eighths"
+    ],
+    "type": "string"
+  },
+  "tempo": {
+    "enum": [
+      "follow",
+      "fixed"
+    ],
+    "type": "string"
+  },
+  "time_signature": {
+    "enum": [
+      "2/4",
+      "3/4",
+      "4/4",
+      "5/4",
+      "6/4",
+      "7/4",
+      "9/4",
+      "12/4",
+      "6/8",
+      "9/8",
+      "12/8"
+    ],
+    "type": "string"
+  },
+  "timing": {
+    "enum": [
+      "performance",
+      "quantized"
+    ],
+    "type": "string"
+  }
+}

addedInput schema / properties / pro_options / type
```
Added value: +"object"
```

addedInput schema / properties / provider / description

Added value: +"local (one instrument or voice), piano (solo piano) or mirelo (a band: uses credits, priced first)."

addedInput schema / properties / replay_only / description

Added value: +"Test accounts only: reuse an exact saved band result, never new processing."

addedInput schema / properties / review_instruments / description

Added value: +"Band only: true (default) holds it for the instrument list before the price."

addedInput schema / properties / score_id / description

Added value: +"The finished or stopped score whose recording is used."

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). The original's by default."

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

Changed2 schema fields changedOct 17, 2026

addedInput schema / properties / consent

Added value: +{
+  "default": false,
+  "type": "boolean"
+}

addedInput schema / properties / credits

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

Changed1 schema field changedOct 16, 2026
- addedInput schema / properties / preview
```
Added value: +{
+  "default": false,
+  "type": "boolean"
+}
```
First observedOct 8, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Goes well beyond the annotations: it explains that credit consumption recurs, that without credits plus consent=true the call returns needs_confirmation and creates nothing, and that the source score survives. destructiveHint=false is corroborated rather than contradicted by 'the original stays', and the non-idempotent cost behavior is surfaced in plain language.

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

Conciseness5/5

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

Three sentences, each carrying distinct information: what it makes, when to call it, and the credit/consent gate. The core constraint ('the original stays') is front-loaded.

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?

Given 9 parameters, a nested pro_options object and no output schema, the description covers the risky part of the call — the confirmation loop — and leaves the enumerated options to the schema. A brief note on what a successful call returns (new score id) would close the remaining gap.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3; the description earns an extra point by explaining how consent and credits interoperate through the needs_confirmation response, which the schema documents only piecewise. It does not describe the view/provider/preview options, but the schema already defines those in detail.

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?

States a specific verb and resource ('Transcribe a score's original recording again as a new score') and adds the decisive scope fact that the original is preserved. That separates it from transcribe_attachment and transcribe_link, which start from a new source rather than an existing score's recording.

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?

Gives an explicit positive trigger ('Only when the user asks for a new transcription') and an explicit negative one ('never merely to fix notation'). It stops short of naming the sibling an agent should use instead for notation corrections (e.g. edit_score/revise_score), leaving that inference to the reader.

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?