Skip to main content
Glama

get_track_routing

Read a track's input/output routing and monitoring settings, including available I/O options for tracks, returns, or the master, to inspect signal flow in Ableton Live.

Instructions

Read a track's input/output routing and monitoring, with the options Live offers for each (names as shown in Live's I/O section, in Live's language).

Parameters:

  • track_index: Index of the track (return index for "return", ignored for "master")

  • track_type: "track" (default), "return" or "master" (these two only have an output)

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

Input Schema

NameRequiredDescriptionDefault
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the disclosure burden. It establishes that this is a non-mutating read and that returned names follow Live's own I/O vocabulary, which is genuinely useful, but it says nothing about what happens with an out-of-range index or a missing device.

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?

Purpose is front-loaded in one sentence and followed by a compact parameter list. The parenthetical 'names as shown in Live's I/O section, in Live's language' restates the same idea twice, a small amount of waste in an otherwise tight definition.

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?

With an output schema present, the description need not describe return values, and both parameters are explained with edge cases. The remaining gap is routing guidance versus set_track_routing and get_track_info, which would help an agent pick correctly among the read tools.

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

Parameters5/5

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

Schema coverage is 0%, and the description fully compensates: it explains that track_index is a return index when track_type is "return" and ignored for "master", and that track_type takes track/return/master with track as the default. These are non-obvious semantics the bare schema does not convey.

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 opens with a specific verb and resource: read a track's input/output routing and monitoring. That clearly separates it from the write-side sibling set_track_routing and from get_track_info, though it never names those siblings explicitly.

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?

Usage is only implied by the read verb; there is no statement of when to choose this over set_track_routing or get_track_info. The note that return and master tracks only have an output is useful context for choosing parameter values, but it is not when-to-use guidance.

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