Skip to main content
Glama

mcp_opendaw_create_send

Create a parallel FX send bus from an audio unit, routing a copy of the signal to a new effects chain while the original signal remains unchanged.

Instructions

Create a parallel FX send bus from an audio unit.

Creates a NEW AudioBusBox (FX bus) with its own AudioUnitBox, then sends a copy of src_unit's signal to that FX bus via AuxSendBox. The dry signal continues to the main output unchanged — this is a parallel send, not a redirect.

After creating the send, add effects (Reverb, Delay) to the FX bus unit using add_effect(fx_unit_index, effect_type). The FX bus unit index is returned.

src_unit: Source audio unit index (the instrument sending signal). name: Name for the FX bus (e.g. "Reverb Bus", "Delay Bus"). send_level_db: Send level in dB (-∞ to +12). -6dB is a good starting point. routing: 'pre' (pre-fader) or 'post' (post-fader, default).

Returns send_index on src AU, and fx_unit_index (the new FX bus AU index for adding effects).

Workflow: create_instrument_track → create_send → add_effect(Reverb on fx_unit_index)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
routingYes
src_unitYes
send_level_dbYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

In the absence of annotations, the description carries the full burden. It explains the creation of new internal objects (AudioBusBox, etc.) and the signal flow (dry signal unchanged). It states the return indices. However, it does not explicitly address error cases (e.g., invalid src_unit) or performance implications. Still, the behavioral coverage is strong.

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 well-structured: a concise opening sentence, followed by technical details, parameter breakdown, return info, and a workflow example. It is detailed without being verbose; every sentence contributes necessary information.

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?

Given the tool's complexity (creating multiple bus/unit objects) and the presence of an output schema, the description covers all essential aspects: what is created, parameter details, return values, and usage workflow. An agent can confidently invoke this tool based on the description alone.

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 input schema has 0% description coverage, so the description must compensate fully. It does so by explaining each parameter: src_unit (source unit index), name (FX bus name), send_level_db (range -∞ to +12 with suggested value), routing ('pre' or 'post' with default). This adds critical meaning absent from the schema.

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 it creates a parallel FX send bus, distinguishes it from a redirect, and explains the internal components (AudioBusBox, AudioUnitBox, AuxSendBox). The purpose is specific and unambiguous. Among siblings, there is no other create_send tool, but it differentiates from general audio bus creation tools.

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?

The description provides explicit workflow guidance: create_instrument_track → create_send → add_effect. It explains when to use this tool (parallel send) and what not to do (redirect). Parameter constraints are given with examples (e.g., send_level_db -∞ to +12, -6dB suggested). This leaves no ambiguity for the agent.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/AMEOBIUS-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server