Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Ghost Notes

ghost_notes

List or remove ghost notes (parenthesized notes) per bar in a MuseScore score. Review the list before removal; a chord made only of ghost notes becomes a rest.

Instructions

List the ghost notes (notes in parentheses) per bar, or remove them (mode='remove'). A chord made only of ghost notes becomes a rest. Show the list to the user before removing: whether a chart keeps ghost notes is their choice.

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

Input Schema

NameRequiredDescriptionDefault
modeNoList them, or remove themlist
drumsNoOnly these drums, e.g. ["hi-hat"]
pitchesNoOnly these MIDI pitches
last_staffNoLast staff (0-based, inclusive). Defaults to the last staff.
end_measureNoLast bar (inclusive). Defaults to the end of the score.
first_staffNoFirst staff (0-based)
start_measureNoFirst bar (1-based position)

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 must carry the full burden, and it does disclose one important side effect: a chord made entirely of ghost notes becomes a rest after removal. It still says nothing about reversibility/undo, permissions, or what the removal response reports, which are material gaps for a mutating tool with zero annotation coverage.

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 short sentences, front-loaded with the action, followed by the side effect and then the user-consent rule. No filler or repetition of schema content.

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 7-parameter tool with no annotations and no output schema, the description covers purpose, the destructive side effect, and a confirmation workflow, but leaves the return shape (how the per-bar list is presented) and reversibility unstated.

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%, so every parameter (mode, drums, pitches, staff/measure ranges) is already documented in the schema; baseline is 3. The description adds the consequence of mode='remove' beyond the terse enum text, but says nothing additional about how the filters combine.

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 concrete verbs (list, remove) against a specific resource (ghost notes), and even defines the domain term as 'notes in parentheses' scoped 'per bar'. It is clearly distinct from the sibling note-editing tools, but it never explicitly contrasts itself with any of them.

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 a clear conditional workflow: list first, show the list to the user, then remove only if they choose, since keeping ghost notes is a stylistic preference. It lacks any explicit exclusions about when this tool is not the right choice versus siblings such as highlight_notes or clear_highlights.

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