Skip to main content
Glama

mcp_opendaw_create_midi_echo

Generate echoing MIDI note repeats with decaying velocity and optional pitch shifting for creative delay effects like guitar throws and synth fills.

Instructions

Create MIDI echo — repeat notes with decaying velocity and optional pitch shift.

Takes existing notes from a region and creates echoing repeats. Each repeat is delayed by delay_beats, quieter by velocity_decay factor, and optionally shifted in pitch. This is a creative effect, not a simple copy — think guitar delay throws, synth echo fills, vocal repeat stutters.

feedback_mode:

  • "linear" — each repeat is velocity_decay × previous (0.6 → 0.6, 0.36, 0.216)

  • "exponential" — faster decay, squared each time

  • "constant" — same velocity for all repeats (stutter feel)

  • "reverse" — each repeat gets louder (build-up feel)

pitch_shift: semitones added per repeat (0 = no shift, +12 = octave up each repeat, -5 = perfect fourth down each repeat). Creates cascading echoes.

dest_track: -1 = same track (thickening), N = separate track (layered echo). Using a separate track lets you process the echo independently.

repeats: 1-8 echo repeats. Each repeat copies ALL notes from the source. delay_beats: time between each repeat (0.25 = 16th, 0.5 = 8th, 1.0 = quarter).

unit_index: AU index. track_index: Source note track. region_index: Source region (-1 = first). repeats: Number of echo repeats (1-8). delay_beats: Delay between repeats in beats. velocity_decay: Velocity multiplier per repeat (0-1, 0.6 = 60% each time). pitch_shift: Semitones added per repeat (0 = none). dest_track: Destination track (-1 = same, N = separate track). feedback_mode: linear / exponential / constant / reverse.

Returns echo summary with per-repeat velocity and pitch info.

Example:

Guitar-style echo: 3 repeats, 8th note delay, decaying

create_midi_echo(0, 0, repeats=3, delay_beats=0.5, velocity_decay=0.5)

Cascading octave echoes on separate track

create_midi_echo(0, 0, repeats=4, delay_beats=0.25, pitch_shift=12, dest_track=2)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repeatsNo
dest_trackNo
unit_indexYes
delay_beatsNo
pitch_shiftNo
track_indexYes
region_indexNo
feedback_modeNolinear
velocity_decayNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries full burden. It adequately describes the behavior: taking notes from a region, creating repeats with decaying velocity and optional pitch shift, feedback modes, and dest_track options. Missing details on error handling or prerequisites, but overall sufficient.

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 description is well-structured with a clear opening, parameter explanations, and examples. It is slightly verbose but every sentence adds value; front-loaded with the core purpose.

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 complex creative tool with 9 parameters and no annotations or output schema provided, the description is highly complete. It explains all parameters, provides examples, and mentions return type. The agent has enough information to use the tool correctly.

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%, but the description thoroughly explains each parameter with purpose, default values, and possible values (e.g., feedback_mode options, pitch_shift range). It adds significant meaning beyond the schema's minimal titles.

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 'Create MIDI echo — repeat notes with decaying velocity and optional pitch shift.' It uses a specific verb ('create') and resource ('MIDI echo'), and distinguishes itself by describing it as a creative effect (not a simple copy), contrasting with siblings like copy tools.

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

Usage Guidelines4/5

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

The description provides context for when to use the tool (creative effect like guitar delay, synth echo) and explains parameter effects with examples, but does not explicitly compare to alternatives among the many sibling tools, lacking when-not guidance.

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