Skip to main content
Glama
Sign In
MuseScore MCP Server

MuseScore MCP Server

by ghchen99
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Add Note

add_note

Insert a note at the current score cursor using a MIDI pitch and note duration; write melodies sequentially or stack pitches into the current chord.

Instructions

Add a note at the current cursor position with the specified pitch and duration. Sequential notes write a melody. Set add_to_chord=True to stack a pitch on the current chord.

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

Input Schema

NameRequiredDescriptionDefault
pitchNoMIDI pitch value (0-127, where 60 is middle C)
durationNoDuration as {"numerator": int, "denominator": int} (e.g. {"numerator": 1, "denominator": 4} for a quarter note)
add_to_chordNoIf True, add this pitch to the current chord instead of writing the next melody note
advance_cursor_after_actionNoWhether to move cursor to next position after adding note

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 discloses that the tool writes at the cursor, builds melodies sequentially, and can stack pitches on a chord, but it does not discuss mutation side effects, undo behavior, or cursor-advancement implications beyond the schema.

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?

The description is three short sentences, front-loaded with the core action and followed by concise behavioral context. Every sentence contributes useful meaning without repetition or filler.

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 four-parameter insertion tool with no output schema, the description explains the essential action, the melody-vs-chord distinction, and the cursor-position context. It leaves some mutation-related behavior implicit, but the schema covers parameter-level details such as cursor advancement.

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%, so pitch, duration, add_to_chord, and advance_cursor_after_action are already well documented in the input schema. The description reinforces the chord-stacking behavior but adds little 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 states a specific verb and resource: add a note at the current cursor position with pitch and duration. It also distinguishes melody writing from chord stacking via add_to_chord. It does not explicitly differentiate from sibling tools such as add_tied_note or add_rest.

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

Usage Guidelines3/5

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

The description explains the two main usage modes: sequential melody notes and chord stacking with add_to_chord=True. It gives no guidance on when to use this tool instead of related siblings like add_tied_note, add_rest, or add_articulation.

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