Skip to main content
Glama

edit_notes

Destructive

Edit chosen MIDI notes in a clip without rewriting: delete, transpose, shift, quantize, set velocity, length, mute, or probability by beat range and pitch.

Instructions

Change some notes of a MIDI clip without rewriting it: delete, transpose, shift in time, quantize starts to a grid, set velocity or length, mute or unmute, set probability, velocity deviation or release velocity.

Choose notes by start time (from_beats/to_beats) and pitches; with neither, all notes. Notes that would leave the MIDI range or the clip start are skipped and listed. One undo step. To replace all notes use write_clip.

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": {
      "action": "<action>"
    },
    "name": "edit_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
clipNoA clip by address instead of track and slot: t0/s2 (Session slot 2 of t0) or t0/a1 (the second timeline clip of t0, see arrangement list).
slotNoClip slot: the scene row, from 0. Example: 0 for the first scene.
beatsNoFor shift: move by this many beats, e.g. 0.5 or -1.
trackNoTrack address of a Session clip, e.g. t0 (with slot).
valueNoFor probability (0-1), velocity_deviation (-127 to 127) and release_velocity (0-127).
actionYesWhat to do with the chosen notes.
pitchesNoOnly these pitches, e.g. ["C3", "E3"] or ["60"]. Empty: all pitches.
to_beatsNoOnly notes starting before this beat.
velocityNoFor velocity: new velocity 1-127.
semitonesNoFor transpose: e.g. 12 or -5.
from_beatsNoOnly notes starting at or after this beat.
grid_beatsNoFor quantize: grid in beats, e.g. 0.25 for 1/16 notes.
length_beatsNoFor length: new note length in beats.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the safety profile is known. The description adds real context beyond that: out-of-range or pre-clip-start notes are skipped and reported back, and the whole edit collapses into a single undo step. It does not state whether the tool reports how many notes were changed, nor warn that repeat calls (e.g. transpose) compound, which matters given idempotentHint=false.

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?

Content is front-loaded: the scope statement comes first, then note selection, then edge-case behavior, then the alternative tool. The action list partly duplicates the action enum, but pairing each action with its parameter adds value rather than noise, so the length is largely earned.

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 13-parameter mutation tool with no output schema and destructive annotations, the description covers the essentials: what changes, how notes are selected, what happens to invalid notes, and the undo granularity. Remaining gaps are minor but real, notably the return value (does it list affected notes?) and clip/track/slot addressing, which is left entirely to the schema.

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 every parameter is already documented, which sets the baseline at 3. The description does add one genuinely useful rule not spelled out per-parameter: the note-selection window is formed by from_beats/to_beats and pitches, and with neither supplied all notes are targeted. Beyond that it mostly echoes the schema's own per-action parameter mapping.

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?

The description opens with a specific verb and resource ("Change some notes of a MIDI clip") and immediately enumerates the concrete mutations supported (delete, transpose, shift, quantize, velocity, length, mute/unmute, probability, velocity deviation, release velocity). It explicitly separates itself from the sibling write_clip ("To replace all notes use write_clip"), so an agent can choose between them without opening either 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?

It gives a clear condition for use (modify a subset of notes rather than rewriting the clip) and names one explicit alternative with its triggering condition (write_clip for full replacement). Selection guidance is also stated (from_beats/to_beats plus pitches, defaulting to all notes), but there is no exclusion guidance relative to other editing siblings such as update_clip or read_clip.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.