Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Prev Element

prev_element

Moves the cursor to the previous element in a MuseScore score to support backward navigation through notes, rests, and other score objects.

Instructions

Move cursor to the previous element.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden and does not meet it. It does not say whether the cursor wraps or stops at the score start, whether selection changes, whether an error is returned at a boundary, or what the call returns; for a state-mutating navigation tool this is a meaningful gap.

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?

One short, front-loaded sentence with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined compression.

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

Completeness2/5

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

For a stateful cursor tool with no annotations and no output schema, the definition leaves out what an agent most needs: boundary behavior at the first element, what state it returns, and how it fits with get_cursor_info and next_element. The stated purpose is the only thing an agent can rely on.

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?

The tool takes zero parameters and the schema coverage is 100%, so there is no parameter meaning for the description to add. The baseline of 4 for zero-param tools is offset slightly because the description offers no guidance on how the call is parameterized implicitly (e.g., by current cursor position).

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 a specific verb and resource: 'Move cursor to the previous element.' The direction (previous) makes it distinguishable from next_element by intent, though the description spends no words differentiating it from other navigation tools like go_to_measure or go_to_beginning_of_score.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No explicit when-to-use or when-not guidance. The agent must infer that this is a cursor-navigation step in a score-editing workflow from the phrase 'Move cursor' alone; nothing says what to do at the first element, whether to use get_cursor_info afterwards, or when a jump tool would be preferable.

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