Skip to main content
Glama

get_track_info

Retrieve detailed information for an Ableton track, return, or master, including name, mixer state, clip slots, and device chain to inspect and troubleshoot mix routing.

Instructions

One track in detail: name, mixer state, clip slots and device chain. Works for return tracks and the main track too.

Parameters:

  • track_index: The track (for "return", its position among returns; ignored for "master")

  • track_type: "track" (default), "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>"
    },
    "name": "get_track_info"
  }
}

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

B3.3/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does signal this is a read-style detail fetch that supports non-regular tracks. It says nothing about out-of-range index behavior, empty slots, or error conditions, which are the main risks an agent faces when calling it.

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 what is returned, then a tight parameter block with no filler. Every sentence carries information; only the indexing-origin detail is missing rather than any excess present.

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, and the two-parameter surface is mostly covered. What is missing is sibling differentiation and failure-mode behavior, which matter for an agent choosing among the many track-related getters.

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%, so the description must compensate, and it does: it defines the valid track_type values ("track", "return", "master"), states the default, and explains that track_index is interpreted among returns and ignored for master. Only the integer range and indexing origin (0- vs 1-based) remain unstated.

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 clear resource and the fields returned (name, mixer state, clip slots, device chain), and clarifies that return and master tracks are covered. It does not differentiate from siblings like get_track_meters and get_device_info, whose content partially overlaps, so an agent must still guess at boundaries.

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?

No when-to-use guidance is offered beyond which track_type to pick; there is no mention of when to prefer get_track_meters, get_track_routing, or get_device_info instead. The one piece of routing supplied is structural (index semantics per type), not a usage rule.

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