Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Select Custom Range

select_custom_range

Select a custom tick range across staves to retrieve continuous phrasing that spans measure boundaries. Specify start/end ticks and staff indices for precise score selection.

Instructions

Select a custom range of ticks across staves. Useful for retrieving continuous phrasing that spans measure boundaries.

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_tick": "<start_tick>",
      "end_tick": "<end_tick>",
      "start_staff": "<start_staff>",
      "end_staff": "<end_staff>"
    },
    "name": "select_custom_range"
  }
}

Input Schema

NameRequiredDescriptionDefault
end_tickYesEnd of the range in ticks (exclusive)
end_staffYesLast staff index (0-based)
start_tickYesStart of the range in ticks (0-based; a quarter note is 480 ticks, so a 4/4 measure is 1920)
start_staffYesFirst staff index (0-based)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not explain whether this replaces the existing selection, what happens with existing highlights or colors, whether the operation is read-only versus a selection-state change, or whether endpoints are validated. For a selection tool with zero annotation coverage, this leaves important behavior unspecified.

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 short sentences with the core action front-loaded and the use case immediately following. There is no filler or repetition.

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?

The four required parameters are fully documented by the schema, and no output schema is needed because this is a selection action. However, with no annotations and no explanation of selection side effects, it is only minimally complete for an agent that needs to understand how the selection state changes.

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 description coverage is 100%, and the schema already explains tick units, 0-based staff indices, and end_tick exclusivity. The description only restates that the range spans ticks across staves, adding no parameter meaning beyond the schema.

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?

The description uses a specific verb and resource: "Select a custom range of ticks across staves." That distinguishes it from simple measure selection, but it does not explicitly contrast it with sibling tools such as select_current_measure or delete_selection.

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?

It gives a clear usage context: retrieving continuous phrasing that spans measure boundaries. It does not state when not to use it or name alternatives, but the use case is concrete enough to guide selection.

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