Skip to main content
Glama

live12_transport_set_punch

Enables or disables punch-in and punch-out markers so arrangement recording starts and stops at loop boundaries in Ableton Live 12.

Instructions

Enables or disables punch-in and punch-out markers for arrangement recording in Ableton Live 12.

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": {
      "punch_in": "<punch_in>",
      "punch_out": "<punch_out>"
    },
    "name": "live12_transport_set_punch"
  }
}

Input Schema

NameRequiredDescriptionDefault
punch_inYesEnable punch-in recording at loop start.
punch_outYesEnable punch-out recording at loop end.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It says the tool sets punch state but not whether it is idempotent, whether it mutates transport state during playback, whether it requires transport to be stopped, or whether the change is persisted in the set — all important for a transport mutation.

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?

A single tight sentence with the action and subject front-loaded and no filler. It is close to minimal size for the information conveyed, though it leaves room for one clarifying clause about prerequisites.

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 two-boolean tool with a fully documented schema and no output schema, the description covers the basics. However, with no annotations to lean on, it should mention the loop/transport preconditions and confirmation of resulting state, so it is only minimally adequate.

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 coverage is 100%, with both booleans explicitly described in the schema, so the baseline is a 3. The description adds only the phrase 'for arrangement recording,' which frames intent but gives no extra meaning about how punch_in vs punch_out interact with the loop boundaries beyond what the schema already says.

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?

States a specific verb pair (enables/disables) and a specific resource (punch-in/punch-out markers for arrangement recording), so an agent knows exactly what the tool affects. It does not explicitly contrast itself with nearby siblings like live12_transport_set_loop, though the punch-specific framing distinguishes it well enough by name.

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?

There is no guidance on when to use this versus the loop or record tools, and no mention of prerequisites such as whether loop mode must be active for punch markers to take effect. The agent must infer the operational context entirely.

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