Skip to main content
Glama
Sign In
waveform-MCP

waveform-MCP

by jarmstrong158
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

aux_return_add

Add an aux return to a track to receive audio from a specified bus number (0-15) for parallel effects routing, such as applying a shared reverb to multiple tracks sending to that bus.

Instructions

Add an auxreturn plugin to a track so it receives audio from the given bus number (0..15). Pair with send_add(bus_num=N) on source tracks for parallel routing — e.g. drum tracks all send to bus 0, aux-return track applies a single reverb.

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_id": "<track_id>"
    },
    "name": "aux_return_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
bus_numNo
track_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior4/5

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

The description discloses the primary behavior—adding an aux return plugin and receiving audio from the specified bus—but does not mention potential side effects like overwriting existing plugins or error handling when the track doesn't exist. Given no annotations, this is moderately transparent but not exhaustive.

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?

The description is two sentences, free of fluff, and logically structured: it states the action, explains the purpose, and provides a practical example. No redundancy.

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?

For a simple tool that adds an aux return, the description gives sufficient context for an agent to understand when and how to use it, including a typical workflow with send_add. No output schema is needed, and the provided information is complete for its 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?

The bus_num parameter is explained with a range (0..15) and its role in routing, while track_id is implicitly clear as the target track. The schema defines constraints, and the description adds semantic meaning beyond the raw values.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action: 'Add an auxreturn plugin to a track' and specifies the purpose 'so it receives audio from the given bus number'. It also differentiates from send_add by pairing, making the tool's intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It provides explicit guidance on pairing with send_add and gives a concrete example for parallel routing (drum tracks send to bus 0, aux-return applies reverb), making it clear when this tool is appropriate.

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