Skip to main content
Glama
Sign In
Ableton Copilot

Ableton Copilot

by F-Fischer
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

set_loop_region

Set the loop region in the arrangement by specifying start position and length in beats. Use it to isolate a section for playback or editing.

Instructions

Set the arrangement loop region.

Parameters:

  • start: Loop start position in beats from the start of the arrangement

  • length: Loop length in beats (must be > 0)

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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": {
      "start": "<start>",
      "length": "<length>"
    },
    "name": "set_loop_region"
  }
}

Input Schema

NameRequiredDescriptionDefault
startYes
lengthYes
user_promptNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It discloses a constraint (length > 0) and the telemetry purpose of user_prompt, but does not describe side effects, invalid-input behavior, whether the loop must be enabled, or what happens to existing loop settings. For a setter tool, this is minimal disclosure.

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 description is compact with a single purpose sentence and a clear bullet list. It repeats the parameter names already in the schema, but the added descriptions are worth it. No fluff; well-structured.

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?

For a simple setter with no output schema, the description covers the action and parameters adequately. However, it omits how this interacts with looping enabling (sibling enable_arrangement_loop) and whether the loop is automatically activated. This is a notable gap for an agent deciding the full sequence of actions.

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%, but the description fully compensates by providing clear, unit-aware meanings: 'start' is in beats from arrangement start, 'length' is in beats with a positivity constraint, and 'user_prompt' is explained as telemetry. This adds significant value beyond the raw schema.

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 ('Set') and the resource ('arrangement loop region'), with a specific scope. It distinguishes from sibling tools like enable_arrangement_loop (which toggles looping) and set_arrangement_time (which positions playback).

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus alternatives, nor any mention of prerequisites such as enabling the loop via enable_arrangement_loop. The description focuses only on parameters, leaving the agent to infer the relationship with sibling tools.

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