Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Prepare Measure Repeat

prepare_measure_repeat

Select measures on specified staves and return the exact MuseScore clicks needed to add measure-repeat signs, since the plugin API cannot place them directly.

Instructions

Prepare measure-repeat signs: selects the measures that should become repeat signs, on the given staves, and returns what to click in MuseScore. The plugin API cannot place measure-repeat signs itself.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "start_measure": "<start_measure>"
    },
    "name": "prepare_measure_repeat"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsNoSize of the measure-repeat sign: 1, 2 or 4 bars
last_staffNoLast staff (0-based, inclusive). Defaults to the last staff.
end_measureNoLast measure (1-based, inclusive). Defaults to start_measure + bars - 1.
first_staffNoFirst staff (0-based)
start_measureYesFirst measure to turn into a repeat sign (1-based); it repeats the bars before it

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations at all, the description carries the full burden and does disclose two important traits: the tool only prepares/returns click instructions rather than mutating the score, and this limitation comes from the plugin API. It stops short of saying whether the current selection or document state is altered, or what the returned payload looks like.

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?

Two sentences, no filler, and the purpose is front-loaded before the rationale. The second sentence earns its place by explaining the manual-click workflow, though wording like 'selects the measures' is slightly ambiguous about whether a selection actually changes.

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 5-parameter tool with no annotations and no output schema, the description should describe the return value more concretely than 'what to click.' The key framing (prepare now, click in MuseScore) is present, but the shape of the returned instructions and any side effects are left unspecified.

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 defaults, 1-based measures, 0-based staves, and the bars enum are already fully documented. The description adds only the phrase 'on the given staves' and the notion that selected measures become repeat signs, which is marginal value over the schema; 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?

'Prepare measure-repeat signs' is a specific verb+resource, and the description scopes it to 'the measures ... on the given staves' and explains the output ('returns what to click in MuseScore'). It implicitly distinguishes itself from apply-style siblings by noting the API cannot place the signs, but it never names an alternative tool outright.

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 is implied by the workflow described: the agent should call this when it wants measure-repeat signs placed and is prepared to finish the job manually. There is no explicit when-to-use/when-not guidance and no mention of nearby siblings like apply_measure_repeats, collapse_to_repeat, or set_repeat_barlines, so the choice among them is left to inference.

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

Deploy Server

Other Tools