Skip to main content
Glama

mcp_opendaw_create_bass_drop

Generate a descending pitch sweep into sustained sub bass to create a classic bass drop for dubstep, trap, or EDM transitions.

Instructions

Create a bass drop — descending pitch sweep into sustained sub bass.

Generates a pitched sweep downward (the "wub" or "fall") followed by a sustained low note. The quintessential dubstep/bass music drop. Also works for EDM build-and-drop, trap bass falls, and impact transitions.

The tool creates two phases:

  1. Sweep phase: notes descend from start_pitch to end_pitch over sweep_beats

  2. Hold phase: a single sustained note at end_pitch for hold_beats

start_pitch: Starting MIDI pitch for the sweep (default 48 = C3). end_pitch: Landing pitch for the sustained bass (default 24 = C1, sub bass). sweep_beats: Duration of the descending sweep in beats (0.5-8, default 2). hold_beats: Duration of the sustained bass after landing (0-16, default 4). sweep_curve: Pitch curve — "linear" (even), "exp" (fast start, slow landing), "log" (slow start, fast landing). unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the drop begins. velocity: Base velocity (0-1, default 1.0 = maximum impact).

Returns notes created, sweep/hold details.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
velocityNo
end_pitchNo
hold_beatsNo
start_beatNo
unit_indexNo
start_pitchNo
sweep_beatsNo
sweep_curveNoexp
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the full burden. It details the two-phase generation process, parameter roles, and return value. However, it does not clarify if notes are appended or overwritten on the track.

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 purpose statement, context, phase breakdown, parameter list, and return value. It is slightly long but every part is informative.

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 complexity (9 parameters, no required, output schema exists), the description covers the purpose, usage, parameters, output, and genre context comprehensively.

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 description coverage is 0%, but the description thoroughly explains all 9 parameters with defaults, ranges, and musical context, adding significant value beyond 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 the tool creates a bass drop with two phases (sweep and hold). It specifies the sound effect and use cases (dubstep, EDM, trap), distinguishing it from sibling tools like create_buildup or create_riser.

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 explains when to use it (e.g., 'quintessential dubstep/bass music drop') but does not explicitly mention when not to use it or name alternatives.

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