ScoreStarling

Confirm band instruments

confirm_pro_instruments

Idempotent

Confirm a band task's complete instrument list and its rhythm and paper choices; the price comes next and nothing starts before it is accepted. A missing instrument cannot appear and a wrong one takes notes. The same confirmation again reuses the task.

Input Schema

Name	Required	Description
`job_id`	Yes
`instruments`	Yes	Every instrument that plays, or null for automatic parts, included in the same quote/start consent.
`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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed9 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 / instruments / description

Added value: +"Every instrument that plays, or null for automatic parts, included in the same quote/start consent."

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 / replay_only / description

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

First observedOct 8, 2026

TDQS

A3.8/5.0

Behavior4/5

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

The annotations already carry readOnly=false, idempotent=true and destructive=false, so the description's job is context. It delivers that by declaring this an acceptance gate that blocks downstream processing, warning that a missing instrument cannot appear and a wrong one produces wrong notes, and matching the idempotency hint with reuse semantics. The phrasing "a wrong one takes notes" is cryptic enough to blur the warning's force.

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?

Three short sentences with the action and its gating consequence front-loaded; no filler. Some sentences are compressed to the point of ambiguity ("nothing starts before it is accepted"), costing a little clarity against the brevity gained.

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

Completeness3/5

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

For a confirmation tool with a nested pro_options object and no output schema, the description covers workflow position, consequences of bad input, and idempotency. It omits what a successful confirmation returns and whether a second confirmation with a changed instrument list is allowed or rejected.

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 75% and the pro_options block is documented in detail inline, so the schema does the heavy lifting. The description contributes only the high-level idea of a "complete instrument list" and "rhythm and paper choices", saying nothing about job_id, replay_only, or the null-for-automatic-parts case.

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: confirming a band task's complete instrument list plus its rhythm and paper choices. That is concrete enough to separate it from analyze_instruments and choose_engine, though it never names a sibling outright.

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 price comes next and nothing starts before it is accepted" places the call precisely in the workflow as the gate before quoting, and "the same confirmation again reuses the task" tells the agent repeat calls are safe. It stops short of naming the tool that produces the analysis this one confirms.

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?