Skip to main content
Glama

set_track_output_routing

Route a track’s output to a named destination such as Main, a bus track, or Group; resolves exact matches first, then unique partial matches, and reports valid options on failure.

Instructions

Route a track's output to another destination by its display name, e.g. 'Main', a bus track's name, or 'Group'. Exact match first, then a unique partial match. On failure the error lists the valid options.

Parameters:

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

  • routing: Destination name as shown in Live's Audio To menu

  • 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>",
      "routing": "<routing>"
    },
    "name": "set_track_output_routing"
  }
}

Input Schema

NameRequiredDescriptionDefault
routingYes
track_typeNotrack
track_indexYes
user_promptNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose real behavior: fuzzy resolution order, failure mode (error lists valid options), the default track_type, and the telemetry purpose of user_prompt. It omits whether the change is undoable or how existing sends are affected, but the core behavioral contract is present.

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?

Behavior is front-loaded in two sentences, followed by a compact parameter block where each line adds meaning rather than restating the schema. No filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 no explanation; all four parameters are documented, and the matching/error semantics an agent needs to call it correctly are stated. Nothing material is missing for a tool of this complexity.

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%, yet every parameter is explained beyond its name: track_index is scoped to its track_type list, routing is tied to Live's Audio To menu, and track_type's valid values ('track'/'return') are supplied even though the schema defines no enum. user_prompt is clarified as telemetry input.

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: route a track's output to another destination, plus the resolution mechanism (display name). It is clearly distinguishable from the getter sibling, though it never names an alternative 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 implied rather than stated: the agent learns that destinations are named as in Live's Audio To menu and that exact match precedes partial match, but there is no explicit when-to-use versus when-not guidance or named alternative tool.

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