Skip to main content
Glama

set_track_send

Set how much signal a track sends to a chosen return track. Use it to control send levels 0.0–1.0 for reverb, delay, or parallel effect buses in Ableton mixes.

Instructions

Set how much of a track goes to a return track.

Parameters:

  • track_index: The sending track

  • send_index: Which send (0 = A, the first return track)

  • value: Send amount 0.0–1.0

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

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>",
      "send_index": "<send_index>",
      "value": "<value>"
    },
    "name": "set_track_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
valueYes
send_indexYes
track_typeNotrack
track_indexYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden, and it says almost nothing beyond the parameters. It does not state whether the change is undoable, whether the send must already exist, what happens if send_index exceeds available returns, or whether this persists in the session. The 0.0–1.0 range is the only behavioral hint.

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 purpose is front-loaded in a single sentence, followed by a compact parameter list with no filler. Every line earns its place given the empty schema descriptions. Slightly terse on the behavioral side, but not padded.

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 parameter block is thorough for a 0%-coverage schema. However, for a mutation tool with zero annotations, the definition omits error conditions and side effects that an agent would need before calling it.

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%, and the description compensates well: it explains track_index, maps send_index 0 to return A, gives the value range 0.0–1.0, and enumerates track_type values 'track' (default) and 'return' — information present nowhere in the schema. It still leaves ambiguity about whether track_index is a global index or relative to track_type, which keeps it from a 5.

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 gives a specific verb and resource: 'Set how much of a track goes to a return track.' This is clearly distinct from siblings like set_track_volume or set_track_panning, and adjacent-but-different from set_track_routing. It stops short of naming an alternative, but the operation itself is unambiguous.

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?

There is no when-to-use guidance, no mention of prerequisites (e.g., a return track must already exist), and no differentiation from set_track_routing, which is the nearest sibling. The agent must infer the usage context from the one-line purpose statement alone.

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