Skip to main content
Glama

set_track_arm

Arms or disarms a track by index so you can control which Ableton Live track receives incoming audio or MIDI for recording.

Instructions

Arm a track for recording, or disarm it.

Parameters:

  • track_index: The track

  • arm: true arms, false disarms

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

Input Schema

NameRequiredDescriptionDefault
armYes
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It conveys the toggle direction for 'arm' but says nothing about exclusivity (whether arming disarms other tracks), failure modes for an out-of-range index, whether the change is persisted/undoable, or what the response confirms.

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?

One action sentence plus a two-line parameter list, front-loaded and free of filler. Every line carries information the agent needs at call time.

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 described, and the tool is simple with only two required params. Still, with zero annotations and zero schema coverage, the definition leaves index semantics and arm-exclusivity behavior entirely undocumented, which is thin for a state-changing tool.

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 0%, so the description must compensate, and it does partially: 'arm: true arms, false disarms' resolves the boolean polarity, which the bare schema does not. However, 'track_index: The track' adds nothing about indexing base, valid range, or how to obtain the index (e.g., via get_track_info).

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?

States a specific verb and resource: 'Arm a track for recording, or disarm it,' which is unambiguous and clearly distinct from sibling setters like set_track_mute or set_track_solo. It doesn't explicitly name a sibling or boundary case, so it stops short of 5.

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?

There is no guidance on when to arm versus when to use related tools, no prerequisite (e.g., track must exist, valid index range), and no note on whether arming one track affects others. The agent must infer all usage context from the name and the mute/solo siblings.

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