Skip to main content
Glama

live12_transport_play

Starts or resumes Ableton Live 12 song playback: set restart to true to begin from 1.1.1 or the arrangement start marker, or false to continue from the current playhead.

Instructions

Starts or resumes song playback in Ableton Live 12. If restart is true, playback starts from 1.1.1 or arrangement start marker; otherwise playback resumes from current playhead position.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "live12_transport_play"
  }
}

Input Schema

NameRequiredDescriptionDefault
restartNoIf true, restarts playback from 1.1.1. If false, continues from current playhead position.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/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 full burden. It does disclose the meaningful state behavior — where playback begins depending on the playhead — but says nothing about what happens when playback is already running, whether the call waits for transport state, or any error/permission conditions.

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?

Two sentences, zero waste, and the primary action is front-loaded ahead of the conditional behavior. Nothing is padded or redundant.

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 single-boolean transport toggle with no output schema, the description covers the essential semantics. Minor gaps remain around interaction with existing transport state and record mode, but nothing critical to invoking it correctly is absent.

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?

With one parameter and 100% schema description coverage, the baseline is 3. The description slightly enriches the schema by noting that restart targets either 1.1.1 or the arrangement start marker, but otherwise restates the schema's own definition of restart.

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?

States a specific verb and resource ('Starts or resumes song playback in Ableton Live 12'), which cleanly separates it from siblings such as live12_transport_stop, live12_transport_record, and live12_transport_set_tempo. An agent can identify the operation without opening the schema.

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 explains the two operating modes (fresh start vs. resume), which implicitly tells the agent when to pass restart, but it never names alternatives or exclusions (e.g., use live12_transport_stop before restarting, or how this interacts with record mode). Usage is implied rather than stated.

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