Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Measures

delete_measures

Remove whole measures from every staff in a score, like MuseScore's Ctrl+Del. When deleting several ranges, start from the last one since later measures renumber.

Instructions

Remove whole measures (on every staff) from the score, like MuseScore's Remove selected range (Ctrl+Del). Works with multi-measure rests on (they are switched off meanwhile) and reports an error if MuseScore deleted fewer measures than asked. Later measures are renumbered, so when removing several ranges start from the last one.

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": "delete_measures"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_measureNoLast measure to remove (1-based, inclusive). Defaults to start_measure.
start_measureYesFirst measure to remove (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses that multi-measure rests are switched off during the operation, that an error is reported if MuseScore deleted fewer measures than requested, and that measures are renumbered. It does not say whether the deletion is undoable or what the error 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences, front-loaded with the verb and scope, then behavioral details and the ordering rule. The Ctrl+Del analogy is compact and earns its place; nothing is redundant.

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 two-parameter destructive tool with no annotations and no output schema, the definition covers scope, side effects, error behavior and ordering caveats. Only reversibility/undo and the failure mode's practical consequence are left out.

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 coverage is 100% and already documents 1-based, inclusive indexing and the end_measure default. The description adds only indirect meaning about ranges ('removing several ranges'), so schema does the heavy lifting; baseline 3.

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 verb and resource ('Remove whole measures') plus the scope that distinguishes it from a general selection delete: every staff, whole measures, analogous to MuseScore's Remove selected range (Ctrl+Del). An agent can tell this apart from delete_selection without opening either schema.

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

Usage Guidelines4/5

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

The scope cue ('whole measures on every staff') implicitly steers selection-based deletion to delete_selection, and the definition gives real operational guidance: start from the last range when removing several, because later measures are renumbered. No sibling is named explicitly, so routing is implied rather than stated.

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