Skip to main content
Glama

live12_take_lane_list

Query all take lanes on a specified track in Ableton Live 12 to inspect comping lanes using a zero-based track index.

Instructions

Queries all take lanes on a track in Ableton Live 12 (Track.take_lanes).

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>"
    },
    "name": "live12_take_lane_list"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_indexYesZero-based track index.

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 must carry the behavioral burden. 'Queries' implies a read-only operation, but the description does not state what is returned, whether results are ordered, or whether the Live session must be connected.

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 filler. Every element, including the Live version and object path, contributes to locating the resource.

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 read tool with 100% schema coverage, the description gives enough context to invoke it correctly. The only minor gap is that it does not explicitly mention the return format, though 'Queries all take lanes' makes the result shape fairly obvious.

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 `track_index` parameter is fully documented in the schema as zero-based and required. The description adds no parameter meaning beyond what the schema already provides, so the baseline 3 is appropriate.

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 uses a specific verb, 'Queries', and a precise resource, 'all take lanes on a track', and references the Live object path `Track.take_lanes`. This clearly distinguishes the tool from sibling take-lane tools such as `live12_take_lane_create` and `live12_take_lane_comp_region`.

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 purpose implies this is the inspection/list tool for take lanes, but the description gives no explicit when-to-use guidance, prerequisites, or alternatives. It does not say when to use this instead of `take_lane_create` or `take_lane_comp_region`, though the intended usage is 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