Skip to main content
Glama

clear_notes_from_clip

Wipe all MIDI notes from a session or arrangement clip to reset it before writing a new note list, enabling a read-edit-write workflow. Use remove_notes for partial edits.

Instructions

Remove every note from a clip. Together with get_clip_notes and add_notes_to_clip this gives read → edit → write: read the notes, change the list, clear the clip, add the new list. For part of a clip use remove_notes.

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

  • 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>"
    },
    "name": "clear_notes_from_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
clip_indexYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.3/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 burden. It clearly discloses the blast radius (all notes removed, not some), but says nothing about reversibility, whether playback must be stopped, or permission requirements. The destructive scope is well conveyed; the operational context is not.

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?

Front-loaded with the core action, then the workflow rationale, then parameters as a scannable list. The read→edit→write sentence is slightly indirect for a clear-only tool but earns its place by justifying why clearing exists.

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 three parameters are addressed. What remains missing is the mutation's severity profile (undoable? blocked during playback?), which matters for a tool that wipes data and has no annotations to lean on.

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

Parameters4/5

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

Schema description coverage is 0%, so the description has to compensate and largely does: it supplies the location values ('session' default or 'arrangement') that the schema lacks as an enum, and clarifies clip_index means 'session slot, or position in get_arrangement_clips' depending on location. track_index is left as the bare tautology 'The track.'

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: 'Remove every note from a clip.' The scope word 'every' plus the explicit contrast with remove_notes ('For part of a clip use remove_notes') lets an agent distinguish it from the closest sibling without opening any schema.

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?

Names the exact alternatives and the conditions that select them: get_clip_notes and add_notes_to_clip for the surrounding read→edit→write workflow, and remove_notes for partial removal. This is explicit when-to-use plus when-not-to-use guidance.

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