Skip to main content
Glama

add_notes_to_clip

Adds MIDI notes to a clip while keeping existing notes intact, so you can layer or extend patterns without clearing the clip first.

Instructions

Add notes to a clip; existing notes stay. To replace notes, clear the clip (clear_notes_from_clip) or a range (remove_notes) first.

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

  • notes: [{"pitch": 60, "start_time": 0.0, "duration": 1.0, "velocity": 100, "mute": false}, ...] with start_time in beats from the clip start

  • location: "session" (default) or "arrangement"

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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "notes": "<notes>"
    },
    "name": "add_notes_to_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesYes
locationNosession
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.6/5.0
Behavior4/5

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

No annotations are supplied, so the description carries the burden, and it does disclose the key behavioral trait: this is an additive merge, not a replacement, and start_time is interpreted relative to clip start. It stops short of covering failures (missing clip/track), permission needs, or what happens on duplicate pitch/position collisions.

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?

The critical semantic ('existing notes stay') is front-loaded and the parameter block is compact. A couple of lines are near-empty filler (e.g. 'track_index: The track'), but nothing is bloated.

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?

An output schema exists, so return values need no explanation, and all four parameters plus the merge semantics are covered. Remaining gaps are error/precondition behavior and some note-field constraints, minor for a write tool of this size.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the notes parameter is a bare array with generic additionalProperties, so the description is the only documentation. It defines all four parameters in prose, clarifies clip_index means session slot or position in get_arrangement_clips, and gives a concrete note-object example with units (beats from clip start).

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 ('Add notes to a clip') plus the crucial additive qualifier ('existing notes stay'), which immediately distinguishes it from sibling mutators like clear_notes_from_clip and remove_notes.

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

Usage Guidelines5/5

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

Explicitly names the alternative path: to replace notes, use clear_notes_from_clip (whole clip) or remove_notes (a range) first. That is a clear when-to-use-this vs when-to-use-another routing statement.

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