mcp-score

Overview Schema Source Related Servers Discussions Admin

add_live_rehearsal_mark

Add a rehearsal mark (e.g., 'A', 'B', 'Intro') to a specific measure in a live score. Specify the measure number and text to update the score in real time.

Instructions

Add a rehearsal mark to a measure in the live score.

Args: measure: Measure number (1-indexed). text: Rehearsal mark text (e.g. "A", "B", "Intro").

Input Schema

TableJSON Schema

Name	Required	Description	Default
`text`	Yes
`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

A3.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It conveys that the tool mutates the live score, but it does not disclose side effects, prerequisites, failure modes, or whether the change is reversible. For a mutation tool with zero annotation coverage, this is a significant gap.

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 description is compact and front-loaded: one clear purpose sentence followed by an Args section. Every sentence earns its place with no fluff or repetition.

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 simple two-parameter tool with an output schema, the description covers the core invocation details. However, it is incomplete in context: it does not mention that the score app must be connected, what happens if the measure is invalid, or any side effects of adding the mark. The missing behavioral and usage context matters more because no annotations exist.

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%, and the description fully compensates by documenting both parameters. It clarifies that 'measure' is 1-indexed and gives concrete examples for 'text' such as 'A', 'B', and 'Intro', adding meaning well beyond the raw schema types.

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?

The description states a clear action and resource: 'Add a rehearsal mark to a measure in the live score.' This distinguishes it from sibling tools like add_live_dynamic, add_live_chord_symbol, and add_live_note by naming a unique object type.

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 context is only implied: an agent can infer it should call this when adding a rehearsal mark to a measure, but the description gives no explicit guidance about prerequisites, when not to use it, or alternatives. It does not mention that a live score connection is required or how this differs from similar add operations.

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