Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Set Measure Number

set_measure_number

Set a bar's displayed measure number by applying an offset that carries to later bars, or exclude the bar from measure counting.

Instructions

Set the displayed number of one bar: add_to_number is MuseScore's 'Add to measure number' (the offset carries on to all later bars), exclude_from_count is 'Exclude from measure count'.

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": {
      "measure": "<measure>"
    },
    "name": "set_measure_number"
  }
}

Input Schema

NameRequiredDescriptionDefault
measureYesBar position (1-based)
add_to_numberNoValue for 'Add to measure number' (0 to remove an offset)
exclude_from_countNoValue for 'Exclude from measure count'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/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 burden. It does disclose one genuinely important side effect — that the add_to_number offset 'carries on to all later bars' — but it says nothing about persistence, whether playback or bar counts are affected, whether a selection is required, or what the tool returns.

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?

A single sentence with no filler, and the core purpose is front-loaded before the parameter glosses. The two quoted MuseScore labels and the parenthetical make it dense but still readable; a short bulleted split would scan slightly better.

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?

With only three shallow parameters at full schema coverage and no output schema, the definition is close to sufficient. What is missing is behavioral context appropriate to a mutation tool with zero annotations: persistence of the setting, effect on playback/counting, and error behavior for an out-of-range bar position.

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 coverage is 100%, so the schema already documents all three parameters, making 3 the baseline. The description earns above baseline by mapping each parameter to MuseScore's own UI labels and by explaining the downstream consequence of add_to_number (the offset propagating to later bars), which is semantics the schema does not convey.

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?

The description names a specific verb and resource: 'Set the displayed number of one bar', which is precise about what changes (the displayed number, not the underlying bar structure). It does not name or distinguish against any sibling such as insert_measure or number_bars_as_played, but the operation itself is unambiguous.

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 only implied: 'displayed number' hints that this is a cosmetic/display edit rather than a structural one, which helps an agent avoid confusing it with insert_measure or append_measure. There is no explicit when-to-use, when-not-to-use, or named alternative, so an agent must infer the boundary with the many other measure-related siblings.

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