Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Rehearsal Mark

add_rehearsal_mark

Adds a rehearsal mark such as “A” or “Verse” at the start of a specified measure to label score sections; check the score afterward because this feature is experimental.

Instructions

Add a rehearsal mark (section label such as 'A' or 'Verse') at the start of a measure. Experimental: check the score afterwards.

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>",
      "text": "<text>"
    },
    "name": "add_rehearsal_mark"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesLabel, e.g. "A" or "Verse 1"
measureYesMeasure number (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden; it does usefully flag the tool as 'Experimental' and warns that the result should be verified, which tells the agent the operation may be unreliable. However, it never states that the score is mutated, whether existing marks at that measure are overwritten, or what preconditions (e.g., cursor/selection) are needed—significant omissions for a write tool with zero annotation coverage.

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?

Two short sentences, front-loaded with the action and resource, and the experimental caveat placed after the core statement. No filler or redundant restatement of the title.

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 two-parameter mutation tool with no output schema and no annotations, the description covers what it does and gives a verification hint, which partly substitutes for a return-value spec. It falls short on mutation effects, overwrite behavior, and preconditions, which an agent needs to invoke it safely.

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 both parameters (text label and 1-based measure number) are already documented. The description adds only the placement semantics 'at the start of a measure', which is marginal beyond 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?

States a specific verb and resource ('Add a rehearsal mark') and concretizes the resource with examples ('section label such as "A" or "Verse"') plus placement ('at the start of a measure'). It doesn't distinguish itself from the sibling add_label or add_text, so an agent may still hesitate between them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use or when-not-to-use guidance is given, and no alternative is named even though add_label and add_text exist as plausible overlaps. The only directive, 'check the score afterwards', is a post-call caution rather than selection guidance.

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