Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Highlight Symbols

highlight_symbols

Highlight or recolor time signatures, repeat barlines, and measure-repeat signs in selected measures to make musical structure easier to spot.

Instructions

Highlight or recolor time signatures, repeat barlines (start/end repeat signs with their dots) and measure-repeat signs. mode='highlight' draws a full-staff-height translucent box around each one (pastel light blue by default); mode='color' recolors the symbol itself (clear=True resets it to black).

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

Input Schema

NameRequiredDescriptionDefault
modeNoBox behind the symbol, or recolor the symbol itselfhighlight
clearNoColor mode only: reset the symbols to black
colorNoColor as "#rrggbb" (default pastel light blue)#a7d8f0
kindsNoWhich symbols
opacityNoBox opacity from 0 to 1 (highlight mode)
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

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries full burden; it does disclose the concrete visual effect of each mode, the default pastel blue, and that clear=True resets symbols to black. It omits that this is a mutating write to the score, whether changes are undoable, and whether repeated calls stack boxes or replace them.

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 action and target objects, then the mode behavior. No filler or redundancy.

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 9-parameter mutating tool with no annotations and no output schema, the definition covers purpose and mode effects but says nothing about reversibility, return values, or how the range parameters constrain the operation. Adequate but with clear gaps given the tool's complexity.

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 descriptions already explain mode, clear, color, kinds, and staff/measure bounds, so the description mostly restates them. It adds nothing about opacity semantics, how kinds interacts with mode, or the 0-based staff vs. 1-based measure convention.

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 specific verbs (highlight, recolor) against three enumerated engraving objects (time signatures, repeat barlines, measure-repeat signs). Listing the exact symbol types distinguishes it from siblings like highlight_bars and highlight_markings without needing to name them.

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?

Explains the two operating modes and when each applies (box behind vs. recolor the symbol, with clear=True as a reset), which is genuine mode-selection guidance. It gives no guidance on when to pick this tool over highlight_bars/highlight_markings, no preconditions, and no statement about scope limits.

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