Skip to main content
Glama

read_track

Read-onlyIdempotent

Inspect a single Ableton Live track by address, including mixer, routing, device chains, Drum Rack pads, Session and Arrangement clips, monitoring, and freeze state.

Instructions

One track in detail: mixer (volume, pan, sends to each return), input and output routing, the device tree with rack chains and Drum Rack pads, Session clips by slot, and Arrangement clips.

Every device comes with its address (t1/d0/c0/d1) for read_device. Also shows monitoring, crossfader assignment, freeze state and the playing slot. Works for return tracks (rA) and the master (m) too.

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": "<track>"
    },
    "name": "read_track"
  }
}

Input Schema

NameRequiredDescriptionDefault
trackYesTrack address: t0 for the first track (numbers from 0), rA for return track A, m for the master. Example: t2

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is settled. The description adds genuine return-shape detail (device addresses, monitoring, crossfader assignment, freeze state, playing slot), which is valuable given there is no output schema. It says nothing about pagination, size limits, or behavior for an invalid track address, so it is useful but not rich.

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?

Content is front-loaded: the first sentence states exactly what is returned, the second covers the device-address affordance and edge-case applicability. It is dense with concrete nouns rather than filler, though the long comma-separated enumeration is somewhat list-like and could be tightened.

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 no output schema, the description carries the burden of explaining return content, and it does so across mixer, routing, devices, and clips, including which fields (monitoring, freeze, playing slot) appear. The remaining gap is failure behavior for a bad address and any indication of response size for large sets; minor for a single-object read 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 100% and the single 'track' parameter is fully documented with addressing rules (t0-based numbering, rA, m) and an example. The description restates the return/master applicability but adds no syntax or format detail beyond the schema. Baseline 3 applies when the schema carries the parameter semantics.

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 the resource (one track) and enumerates its concrete contents: mixer with volume/pan/sends, input-output routing, device tree with rack chains and Drum Rack pads, Session and Arrangement clips. It also distinguishes scope from read_device by explaining that device addresses are supplied for that sibling. It stops short of a single crisp verb phrase like 'Read one track', but an agent can still tell what it returns.

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?

Routing guidance is present but indirect: device addresses are handed out 'for read_device', implying this tool gives the overview and read_device drills into a single device. It also states applicability beyond regular tracks ('Works for return tracks (rA) and the master (m) too'). There is no explicit when-not or exclusion, so it falls short of a full 5.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.