Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Delete Selection

delete_selection

Delete the current selection in MuseScore or remove a specific 1-based measure number. Use it to clear notes, rests, or measures while editing a score programmatically.

Instructions

Delete the current selection, or the specified measure.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "delete_selection"
  }
}

Input Schema

NameRequiredDescriptionDefault
measureNoMeasure number (1-based) to delete. If omitted, the current selection is deleted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. 'Delete' makes the destructive nature clear, but it says nothing about irreversibility, undo availability, permission requirements, or what happens if there is no current selection.

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 short sentence with the default behavior (current selection) front-loaded before the override case. Nothing is wasted, though the sentence is terse enough to feel slightly under-specified rather than padded.

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 one-parameter, no-output-schema mutation tool this is the minimum viable description. It omits the outcome of a successful deletion and any failure conditions, which an agent would need for a destructive operation with no annotations.

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% and the single parameter is fully documented, including the 1-based numbering and the omit-to-use-selection fallback. The description only restates that fallback and adds no syntax or edge-case detail beyond the schema.

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 pairs a specific verb ('Delete') with a specific resource ('the current selection, or the specified measure'), so an agent knows exactly what is removed. It is reasonably distinguishable from the sibling delete_measures, though it does not explicitly contrast itself with that tool.

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?

The description implies the two modes of use: omit the measure to delete the current selection, or supply a measure number to delete that measure. However, it never states when to prefer this tool over the sibling delete_measures, nor any precondition such as requiring an active selection.

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