Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Beam Over Rests

beam_over_rests

Beam eighths and shorter notes across rests within a beat group to create drum-chart style beamed groups with rests under the beam. Use clear=True to restore automatic beaming.

Instructions

Beam eighths and shorter across rests inside a beat group (a dotted quarter in 12/8, a beat in 4/4), as drum charts write them: one beamed group per beat with the rest under the beam, instead of separate flags broken at every rest. Only rests with beamable notes before and after them in the same group change. Run it over the whole drum staff once the chart is done. clear=True puts the rests back on automatic beaming.

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

Input Schema

NameRequiredDescriptionDefault
clearNoUndo: put the rests back on automatic beaming
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

A4.2/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 behavioral burden. It does well on scope of change (only rests flanked by beamable notes in the same group are affected) and documents the undo path (clear=True restores automatic beaming), but says nothing about whether existing manual beams are overridden, whether the operation is idempotent, or what happens on non-drum staves. A genuine mutation tool would benefit from more of that.

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?

Front-loaded with the purpose, then scope of effect, then usage timing, then the undo flag — a sensible ordering with no filler sentences. Dense musical jargon ('beat group', 'beamable') is appropriate for the audience but makes a couple of clauses need re-reading.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, but for a notation-formatting tool with five fully documented parameters and no annotations, the description supplies everything needed to call it correctly: the domain concept, the precise effect boundary, the operational timing, and the undo mechanism.

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 schema already documents all five parameters, and the description correctly stays out of the way while reinforcing the semantics of clear=True as an undo switch. The mention of running 'over the whole drum staff' implicitly confirms the staff-range defaults, adding a small amount of meaning beyond the schema.

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 (beam) and a precisely scoped resource (eighths and shorter notes across rests inside a beat group), with concrete examples of the grouping unit (a dotted quarter in 12/8, a beat in 4/4). The contrast with the un-desired state ('instead of separate flags broken at every rest') makes the intended outcome unambiguous.

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 operating instruction: 'Run it over the whole drum staff once the chart is done,' which tells the agent the timing and scope of application. It also scopes the effect ('Only rests with beamable notes before and after them in the same group change') and names the inverse via clear=True, but never states when not to use it or what to do if the score has no drum staff.

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