Skip to main content
Glama

live12_track_ungroup

Dissolve an Ableton Live 12 group track and promote its member tracks to top level, making individual tracks accessible for further editing and routing.

Instructions

Dissolves an existing group track in Ableton Live 12, promoting its member tracks to top-level.

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": {
      "group_track_index": "<group_track_index>"
    },
    "name": "live12_track_ungroup"
  }
}

Input Schema

NameRequiredDescriptionDefault
group_track_indexYesZero-based index of the group track to dissolve.

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?

With no annotations, the description carries the behavioral burden and does disclose the key side effect: member tracks are promoted to top-level. However, it omits whether the action is reversible/undoable, how nested groups are handled, and whether the group track itself is removed.

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?

A single efficient sentence with the operation front-loaded and the downstream effect clearly attached. No wasted words.

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 low-complexity mutation with one fully documented parameter and no output schema, the description covers the core purpose and effect. It is slightly incomplete on behavioral edges like undoability and nested-group handling.

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?

There is a single parameter with 100% schema description coverage ('Zero-based index of the group track to dissolve'). The description adds no additional syntax or format detail beyond the schema, so the baseline of 3 applies.

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 ('dissolves') and resource ('existing group track in Ableton Live 12') plus the resulting effect on member tracks. No sibling tool performs this operation, so its purpose is unambiguous even without naming an alternative.

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?

The description defines the operation but gives no explicit guidance on when to use it versus alternatives (e.g., track_delete or track_group), nor prerequisites or exclusions. Use is only implied by the verb.

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