mcp-score

Overview Schema Source Related Servers Discussions Admin

transpose_passage

Transpose notes in a selected measure range and staff by a set number of semitones. Uses conventional spelling (e.g., C to Db) while leaving key signatures and chord symbols unchanged.

Instructions

Transpose the notes of a passage by a number of semitones in the live score.

Notes are moved with conventional spelling (a minor second up turns C into Db). Key signatures and chord symbols in the passage are left unchanged.

Args: start_measure: First measure (1-indexed). end_measure: Last measure (inclusive, 1-indexed). staff: Staff index (0-indexed). semitones: Semitones to transpose (positive = up, negative = down).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`staff`	Yes
`semitones`	Yes
`end_measure`	Yes
`start_measure`	Yes

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed4 schema fields changedSep 26, 2026
- addedOutput schema / $defs
```
Added value: +{
+  "CommandResult": {
+    "additionalProperties": true,
+    "type": "object"
+  }
+}
```
- addedOutput schema / properties / result / $ref
```
Added value: +"#/$defs/CommandResult"
```
- removedOutput schema / properties / result / title
```
Removed value: -"Result"
```
- removedOutput schema / properties / result / type
```
Removed value: -"string"
```
First observedv0.1.0May 29, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It adds useful behavior not derivable from the schema: conventional spelling (C to Db), and that key signatures/chord symbols remain unchanged. It doesn't mention undoability or connection requirements, but it does disclose the most important side-effect scoping.

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?

The main operation is front-loaded in one clear sentence, followed by only necessary behavioral notes and a compact parameter list. No filler or redundant restatement of the input schema.

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 four-parameter mutation tool with no annotations, the description covers the operation, parameter semantics, and key behavioral exclusions. It is nearly complete, though it could explicitly mention prerequisites such as an active live-score connection or the in-place/destructive nature of the edit.

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

Parameters5/5

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

Schema description coverage is 0%, so the Args section must compensate. It fully documents all four parameters, including start_measure being 1-indexed, end_measure being inclusive, staff being 0-indexed, and semitones sign direction. This is exactly the added meaning an agent needs.

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 action and target: 'Transpose the notes of a passage by a number of semitones in the live score.' It is immediately distinguishable from siblings like add_live_note or set_live_key_signature, none of which perform transposition.

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?

The intended use is implied by the action and 'live score' context, and the note that key signatures/chord symbols are left unchanged hints at scope boundaries. However, it never explicitly says when to prefer this tool over alternatives or when not to use it.

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