Skip to main content
Glama

remove_notes

Deletes only the MIDI notes inside a specified time window and pitch range, so you can clear one bar or drum lane before adding replacement notes.

Instructions

Remove only the notes starting inside a time window and a pitch range — to rewrite one bar, or one drum lane, then add the new notes.

Parameters:

  • track_index: The track

  • clip_index: Session slot, or position in get_arrangement_clips

  • from_time: Window start, in beats from the clip start

  • time_span: Window length in beats (default: until the clip end)

  • from_pitch: Lowest pitch of the range (0–127)

  • pitch_span: How many pitches from from_pitch (128 = all, 1 = just that note)

  • 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": "remove_notes"
  }
}

Input Schema

NameRequiredDescriptionDefault
locationNosession
from_timeNo
time_spanNo
clip_indexYes
from_pitchNo
pitch_spanNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description carries the full behavioral burden, and it does disclose the key semantic that only notes *starting* inside the window are affected — a real distinction from overlap-based deletion. However, for a destructive mutation it says nothing about undoability, permission requirements, or what happens when zero notes match the window.

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 purpose sentence is front-loaded and the parameter list is scannable, with every line adding information rather than restating a title. It is slightly list-dominant, but no sentence is wasted.

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 7-parameter destructive tool with zero annotation coverage, the definition covers scope, all parameter semantics, and the intended workflow; an output schema exists so return values need not be described. What is missing is the mutation's side-effect profile — reversibility and error behavior — which matters for a delete operation.

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%, so the description must compensate and largely does: it explains units (beats from clip start), defaults (time_span until clip end, pitch_span 128 = all), value ranges (0–127), and even resolves clip_index as 'Session slot, or position in get_arrangement_clips'. The only thin entry is track_index ('The track'), which does not state the indexing base.

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 uses a specific verb ('Remove') plus a precisely scoped resource ('only the notes starting inside a time window and a pitch range'), which tells an agent this is a filtered partial delete rather than a wholesale wipe. It never names the sibling it is contrasted against (clear_notes_from_clip), so the differentiation is inferable rather than explicit.

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 supplies a concrete usage scenario — 'to rewrite one bar, or one drum lane, then add the new notes' — which tells the agent this is a replace-then-reinsert workflow paired with add_notes_to_clip. There are no explicit when-not conditions and no named alternative for the full-clear case, leaving that inference to the agent.

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