Skip to main content
Glama

get_track_output_routing

Show where a track’s audio is routed and list every available output destination, including Main, Group, other tracks, and Sends Only. Use a track index and type to inspect routing.

Instructions

Show where a track's audio goes and every destination it can be routed to (e.g. 'Main', 'Group', other track names, 'Sends Only').

Parameters:

  • track_index: Index of the track (within its track_type list)

  • track_type: 'track' (default) or 'return'

  • user_prompt: The original user prompt that led to this tool call (for telemetry)

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_output_routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
track_typeNotrack
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.4/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 behavioral burden, and it discloses little beyond the resource itself. It never states that the operation is non-mutating, what happens if track_index is out of range, or whether the routing view reflects live session state. The only real behavioral disclosure is the implied read semantics of 'Show' and the enumeration of possible destination values.

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 return semantics are front-loaded in the first sentence and the parameter block is scannable, with no filler prose. The parenthetical example list is a touch verbose but earns its place by disambiguating the word 'destination'.

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?

For a three-parameter read tool with an output schema, the definition covers the resource, its return shape in conceptual terms, and every parameter. The missing piece is safety/error behavior, which is largely mitigated by the output schema documenting the actual return values.

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 description coverage is 0%, so the description must compensate, and it does: it defines all three parameters, clarifies that track_index is scoped to its own track_type list, and documents the 'track'/'return' values for track_type although no enum exists in the schema. Only user_prompt's telemetry purpose is covered thinly and no format hints are given for it.

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 ('Show') and resource ('a track's audio' routing), with concrete examples of the destinations ('Main', 'Group', other track names, 'Sends Only'). An agent understands exactly what is returned, though the description never names the counterpart write tool set_track_output_routing to sharpen the distinction.

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: the 'Show' phrasing signals an inspection operation, and the mention that it returns every routable destination hints that this is how you discover valid targets before routing. There is no explicit when-to-use, when-not-to-use, or reference to alternative tools.

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