Skip to main content
Glama
Sign In
LiveSession MCP

LiveSession MCP

by Uri-Rosen
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

freeze_track

Destructive

Freeze an Ableton Live track and wait for rendering to free CPU from heavy plug-ins; set flatten to bounce it to audio and remove devices, with undo restoring them.

Instructions

Freeze a track (Edit > Freeze Tracks) and wait until Live finishes rendering it; flatten=True instead prints it to audio for good (Edit > Bounce Tracks in Place: the track becomes an audio track and its devices are removed — undo restores them). Frees CPU from heavy plug-ins.

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": "freeze_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
flattenNo
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the destructiveHint=true annotation by specifying exactly what is destroyed in flatten mode (track becomes audio, devices are removed) and that undo restores them. It also discloses the blocking behavior — the call waits for Live to finish rendering.

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?

Front-loaded with the primary action, then the conditional flatten behavior, then the rationale. Dense with parenthetical menu references but nearly every clause adds actionable information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need no explanation, and the description covers the mutation risk, the blocking render wait, and the reversibility of flatten. Nothing an agent needs in order to call this safely is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries the burden and does so for the non-obvious parameter: flatten=True is fully explained in terms of its effect. track_index is left implicit as an obvious ordinal, which is the only small gap.

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 (freeze a track) and immediately names the two operating modes, including the Live menu path each corresponds to. An agent can tell exactly what happens in each mode 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 Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a concrete rationale for use ('frees CPU from heavy plug-ins') and clearly frames flatten=True as the more drastic alternative with its own consequences. It doesn't name sibling tools or state when *not* to freeze, but the context is clear enough to choose correctly.

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