ableton-mind

Overview Schema Source Related Servers Discussions Admin

clip_set_loop

Set loop parameters (start, end, looping) for a target clip in Ableton Live, preserving any unspecified fields. Idempotent operation for precise clip loop edits.

Instructions

Configure a clip's loop_start, loop_end, and/or looping flag while preserving omitted fields. Use for clip loop edits after locating the clip. Idempotent within 1e-4 and verified against only the fields provided by the caller.

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_slot_index": "<clip_slot_index>"
    },
    "name": "clip_set_loop"
  }
}

Input Schema

Name	Required	Description	Default
`track_index`	Yes
`clip_slot_index`	Yes
`loop_start`	No
`loop_end`	No
`looping`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedJun 11, 2026

TDQS

A3.8/5.0

Behavior3/5

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

No annotations provided, so description carries full burden. It discloses idempotency ('Idempotent within 1e-4') and field preservation ('verified against only the fields provided'), but does not mention side effects, required permissions, or error handling.

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?

Extremely concise: two sentences with zero wasted words. The most important information (action, resource, key behavior) is front-loaded.

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

Completeness2/5

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

Given no output schema, no annotations, and 5 parameters with 0% schema description coverage, the description is insufficient. It lacks explanation of index parameters, error conditions, return values, and potential side effects. A more complete description would include usage notes for indices and validation.

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 0%, but description adds value by explaining that omitted fields are preserved and that the tool is idempotent. However, it does not explain track_index and clip_slot_index (required) or provide format details for loop_start and loop_end.

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?

Description clearly states the action (configure), the resource (clip), and specific fields (loop_start, loop_end, looping). The verb 'configure' and resource 'clip' are precise, and the tool is distinct from siblings like clip_set_envelope or clip_set_name.

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?

Explicitly says 'Use for clip loop edits after locating the clip,' providing a clear usage context. While it doesn't mention when not to use or alternative tools, the instruction is sufficient for proper invocation.

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