Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Go To Measure

go_to_measure

Navigates to a specified measure and selects it across all staves, placing the cursor at beat 1 so subsequent note, rest, or lyric tools apply there.

Instructions

Navigate to a specific measure and select it across all staves. The cursor moves to beat 1 of that measure on the first staff, so the next cursor tool (add_note, add_rest, add_lyrics, set_time_signature...) acts there; use next_staff to move down to another staff.

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": {
      "measure": "<measure>"
    },
    "name": "go_to_measure"
  }
}

Input Schema

NameRequiredDescriptionDefault
measureYesMeasure number (1-based, must not exceed the number of measures in the score)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.9/5.0
Behavior3/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 usefully discloses hidden state changes - selection spans all staves and the cursor lands on beat 1 of the first staff - but says nothing about out-of-range behavior, whether prior selections are replaced, or what the tool returns. That is decent side-effect disclosure with notable gaps for a stateful navigation tool.

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?

Two sentences, front-loaded with the action and followed by the consequence for follow-up tools; virtually nothing is wasted. The parenthetical tool list is slightly long but earns its place by making the chaining concrete.

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 a single-parameter navigation tool with no output schema, the definition covers what it does, where the cursor ends up, and how to continue on other staves. Missing only error/edge behavior, which the schema's range note partially absorbs.

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 the 1-based measure numbering and the upper bound are already fully documented in the schema. The description reinforces the semantics by tying the parameter to a resulting cursor position on beat 1 of the first staff, but adds no format or edge-case detail beyond that baseline.

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 ('Navigate to a specific measure and select it across all staves') plus the exact cursor effect, which cleanly separates it from go_to_final_measure, go_to_beginning_of_score, and select_current_measure. An agent can tell what this does without opening the schema.

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?

Explains the downstream context clearly: the next cursor tool (add_note, add_rest, add_lyrics, set_time_signature...) acts at that position, and next_staff is named as the way to reach another staff. It gives strong when-to-use context but never states an explicit exclusion or precondition (e.g., that it does not create or edit anything).

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