Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Clear Highlights

clear_highlights

Remove highlight bands, note boxes, marking boxes, and boxed labels from a range of measures and staves to clean up score annotations.

Instructions

Remove highlights from a range of measures and staves. kinds: 'highlights' = bands and boxes from highlight_bars, highlight_notes and highlight_symbols; 'markings' = boxes behind dynamics (highlight_markings); 'labels' = boxed labels (add_label); 'notes' = small notehead boxes made by older versions. Recolored notes and symbols are reset with clear_color / highlight_symbols(mode='color', clear=True).

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

Input Schema

NameRequiredDescriptionDefault
kindsNoWhat to remove: highlight bands, note boxes, marking boxes, boxed labels
last_staffNoLast staff (0-based, inclusive). Defaults to the last staff.
end_measureNoLast measure (1-based, inclusive). Defaults to the end of the score.
first_staffNoFirst staff (0-based)
start_measureNoFirst measure (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the full burden; it discloses the mutation and enumerates precisely which artifacts are destroyed per kind, including that 'notes' targets legacy notehead boxes. It does not address reversibility/undo, whether clearing an empty range is a no-op or error, or what the call returns, leaving meaningful gaps for a destructive operation.

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?

The action and its scope are front-loaded, followed by the kinds breakdown and the redirect to clear_color. Dense but waste-free; the only mild cost is that the kinds mapping is compressed into one long sentence, which slows scanning slightly.

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?

With 5 optional parameters, full schema coverage, and no output schema, the description covers action, scope, per-kind semantics, and cross-tool routing, which is enough to invoke it correctly. The notable omission is any hint about confirmation, undo, or result reporting for a destructive clear operation.

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 baseline is 3, and the range parameters (first_staff/start_measure/etc.) are already explained by the schema. The description still adds genuine meaning by interpreting each enum value of 'kinds' in terms of the tool that produced that artifact, which the schema's bare enum list does not convey.

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 highlights') plus scope ('from a range of measures and staves'). It then disambiguates itself from siblings by mapping each kind to the tool that created it (highlight_bars, highlight_notes, highlight_symbols, highlight_markings, add_label), so an agent can tell what it does and what it does not do.

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?

Gives an explicit routing rule for an adjacent case: recolored notes and symbols must be reset via clear_color or highlight_symbols(mode='color', clear=True), not this tool. That is real when-to-use-alternative guidance. It does not state prerequisites, ordering relative to undo, or when not to call at all, which keeps it short of a 5.

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