Skip to main content
Glama

live12_transport_set_overdub

Toggles arrangement overdub in Ableton Live 12, letting you enable or disable layered recording over existing arrangement data.

Instructions

Enables or disables arrangement overdub in Ableton Live 12 (Song.arrangement_overdub).

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": {
      "overdub": "<overdub>"
    },
    "name": "live12_transport_set_overdub"
  }
}

Input Schema

NameRequiredDescriptionDefault
overdubYesWhether arrangement overdub is enabled.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly identifies the tool as a state-changing toggle and maps it to Song.arrangement_overdub, but it does not describe persistence, side effects on recording, permissions, or return behavior.

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 a single, front-loaded sentence with no wasted wording. It identifies the action and target immediately.

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 simple one-parameter boolean toggle with a fully described schema and no output schema, the description is nearly complete. A little more context about the effect of arrangement overdub would help, but an agent has enough information to invoke it correctly.

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 100%, and the single boolean parameter is already fully documented in the schema. The description adds the Ableton property mapping but does not provide additional syntax or semantic detail beyond what the schema already states.

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 states a specific verb and resource: enabling/disabling arrangement overdub in Ableton Live 12, with the underlying Song property named. It is clear what the tool does, though it does not explicitly differentiate itself from sibling transport settings such as set_loop or set_punch.

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?

Usage is implied by the setting name: use it when arrangement overdub should be turned on or off. There is no explicit when-to-use guidance, prerequisites, or comparison to alternatives, but the boolean toggle nature makes the intended context reasonably inferable.

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