Skip to main content
Glama

rack_variation

List, recall, store, or randomize macro variations on Ableton racks to save current settings or generate happy accidents for later recall.

Instructions

A rack's macro variations (Live 11+): list them with the current macro values, recall one, store the current macros as a new variation, or randomize the macros (great for happy accidents, then store the result).

Parameters:

  • track_index / device_index: The rack

  • action: list | recall | store | randomize

  • index: Variation to recall

  • track_type: "track", "return" or "master"

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

Input Schema

NameRequiredDescriptionDefault
indexNo
actionNolist
track_typeNotrack
track_indexYes
device_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full burden, and it does disclose that three of the four actions mutate state (recall, store, randomize) while list is read-only, plus the Live 11+ requirement. It does not say what happens to unsaved macro values on recall, whether store overwrites an existing variation, or what randomization scope is affected.

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?

The purpose sentence is front-loaded and the parameter list is compact and scannable. The parameter bullets earn their place by adding meaning absent from the schema, so there is little waste.

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?

An output schema exists, so return values need not be explained. But for a four-action tool with zero schema descriptions, the definition omits action-specific parameter requirements and mutation side effects, leaving meaningful gaps relative to the tool's complexity.

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?

Schema coverage is 0% (no titles beyond bare names, no enums), so the description must compensate, and it does: it defines the action vocabulary, maps index to 'variation to recall', and gives the allowed values for track_type. It falls short of stating which parameters are conditionally required per action (e.g. index only for recall).

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?

The description names a specific resource (a rack's macro variations) and enumerates the four concrete operations: list, recall, store, randomize. An agent can tell exactly what the tool does, though it doesn't differentiate against any sibling tools (none of the listed siblings appear to overlap, so this is a minor gap).

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 parenthetical 'great for happy accidents, then store the result' implies a workflow for randomize, and 'Live 11+' signals an applicability constraint. However, there is no explicit when-to-use/when-not guidance or statement of preconditions for each action, so usage is largely inferred from the action names.

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