Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Highlight Bars

highlight_bars

Highlights selected measures or beats with a semi-transparent color band behind notes, following bars across line breaks. Set measure, beat, staff, color, and opacity; remove highlights as needed.

Instructions

Highlight bars like a highlighter pen: a thick, semi-transparent band behind the notes of each staff in the range, following the bars across line breaks. start_beat/end_beat limit it to part of a bar. Saved in the score; remove with clear_highlights. Experimental: check the result in the score.

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

Input Schema

NameRequiredDescriptionDefault
colorNoHighlight color as "#rrggbb" (default yellow)#ffe600
opacityNoOpacity from 0 to 1
end_beatNoLast beat in end_measure to include, the whole beat (e.g. 4 = through the end of beat 4). Defaults to the end of the measure.
last_staffNoLast staff (0-based, inclusive). Defaults to first_staff.
start_beatNoBeat in start_measure where coloring starts (1-based; fractions allowed, e.g. 3.5 for the 'and' of 3). A beat is the time signature's denominator: a quarter in 4/4, an eighth in 6/8. Defaults to the start of the measure.
end_measureNoLast measure (1-based, inclusive). Defaults to start_measure.
first_staffNoFirst staff (0-based)
start_measureYesFirst measure to highlight (1-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/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 burden and does disclose key behaviors: the highlight is persisted ('Saved in the score'), reversible via clear_highlights, and flagged as experimental with a verify-in-score caveat. It does not say whether existing highlights are overwritten or stacked, or what the tool returns on success.

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?

Three tight sentences: what it draws, how to narrow the range, and how to remove it. The visual analogy is front-loaded and every sentence adds information.

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 an 8-parameter mutation tool with no annotations and no output schema, the description covers persistence, removal, and the experimental caveat. Remaining gaps (interaction with prior highlights, return value, any selection prerequisite) are modest given full schema coverage.

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 the schema itself explains beat/staff indexing in detail, so the baseline applies. The description only adds that start_beat/end_beat restrict the range to part of a bar, which is marginal beyond the schema's own wording.

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 concrete verb and resource with visual specifics ('thick, semi-transparent band behind the notes of each staff'), plus scope ('bars in the range', 'following the bars across line breaks'). That implicitly distinguishes it from note/symbol/marking highlighters, but it never names a sibling to route against explicitly.

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 clear operational context: use start_beat/end_beat to limit to part of a bar, and use clear_highlights to undo. It does not say when to prefer this over highlight_notes or highlight_symbols, so the guidance is contextual rather than exclusionary.

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