Skip to main content
Glama
Sign In
ableton-mcp-lofifren

ableton-mcp-lofifren

by LofiFren
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

remove_notes_from_clip

Delete MIDI notes from a clip using track and clip index. Optionally restrict removal to a specific time or pitch range for targeted editing.

Instructions

Remove MIDI notes from a clip within a specified range. By default removes ALL notes. Use parameters to target specific ranges.

Parameters:

  • track_index: The index of the track containing the clip

  • clip_index: The index of the clip slot containing the clip

  • from_time: Start time in beats (default: 0.0 = beginning)

  • from_pitch: Lowest MIDI pitch to remove (default: 0)

  • time_span: Duration in beats to clear (default: 99999.0 = all)

  • pitch_span: Number of pitches above from_pitch to clear (default: 128 = all)

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_from_clip"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYes
clip_indexYes
from_timeNo
from_pitchNo
time_spanNo
pitch_spanNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.7/5.0
Behavior2/5

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

No annotations exist, so the description must carry the full burden. It explains default behavior and parameter effects but omits crucial details: whether the operation is destructive, requires specific permissions, affects undo history, or has side effects like clearing undo steps. The description is minimal for a mutating tool.

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 extremely concise: a single sentence for purpose followed by a parameter list. Every line adds value, and the default behaviors are efficiently communicated. No redundancy or unnecessary text.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description does not mention return values or confirmation. It also omits error handling (e.g., invalid track or clip indices) and does not clarify if the operation is permanent or undoable. For a simple removal tool, the missing context is acceptable but not fully complete.

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?

The input schema has 0% description coverage (no per-parameter descriptions). The description compensates by listing all 6 parameters, clarifying their roles (e.g., 'from_time: Start time in beats'), and explaining defaults. However, it could better clarify the relationship between time_span and from_time, and pitch_span and from_pitch.

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 clearly states the action ('Remove MIDI notes from a clip') and specifies the scope ('within a specified range'). This distinguishes it from sibling tools like 'add_notes_to_clip' and 'get_clip_notes', which have opposite or different purposes.

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 implies default behavior (remove all notes) but does not explicitly state when to use this tool versus alternatives (e.g., 'quantize_clip' for editing, 'delete_clip' for entire clip removal). No guidance on when not to use it is provided.

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