Skip to main content
Glama

mcp_opendaw_create_impact

Create single-hit transition elements for drops and section changes in EDM tracks. Generates sustained notes with type-specific pitch, duration, and velocity for impactful transitions.

Instructions

Create an impact — single hit transition element for drops and section changes.

Generates a single sustained note with type-specific pitch, duration, and velocity. Essential for EDM transitions: the "hit" that lands after a riser/build-up.

impact_type: Type of impact:

  • "sub_boom" — deep sub bass hit (C1, long decay, dark)

  • "impact_hit" — mid-range punch (C3, medium decay, aggressive)

  • "downlifter" — descending pitch from high to low (glissando fall)

  • "sub_drop" — lowest sub with long tail (B0, very long, cinematic)

  • "punch" — short bright hit (C5, short decay, snappy)

unit_index: AU index (-1 = find first AU with note tracks). track_index: Note track index. start_beat: Position in beats where the impact lands. pitch: Base MIDI pitch (default 36 = C2, overridden by type). length_beats: Duration in beats (default 4 = one bar). velocity: Hit velocity (0-1, default 0.9 = loud).

Returns notes created and impact parameters.

Example:

Sub boom on the downbeat

create_impact(start_beat=0, impact_type="sub_boom")

Downlifter after riser

create_impact(start_beat=4, impact_type="downlifter", length_beats=2)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pitchNo
velocityNo
start_beatNo
unit_indexNo
impact_typeNosub_boom
track_indexNo
length_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so description carries full burden. It explains that it generates a single sustained note with type-specific properties and returns notes created and parameters. Does not disclose side effects or destructive nature, but covers main behavior adequately.

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?

Well-structured: summary line, detailed explanation, parameter list with inline descriptions, and examples. A bit lengthy but every part adds value; could be slightly more concise.

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 7 parameters, no schema descriptions, and no annotations, the description is highly complete. It covers purpose, all parameters with defaults and options, return value, and provides examples for typical use.

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 description thoroughly explains all 7 parameters: impact_type with list of values and characteristics, unit_index, track_index, start_beat, pitch (with default and override), length_beats, velocity. Includes examples with default usage.

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?

Clearly states it creates an impact—a single hit transition element. Distinguishes itself from siblings by specifying it's for drops and section changes, and describes the output as a sustained note with type-specific characteristics.

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?

Gives explicit usage context: 'Essential for EDM transitions: the hit that lands after a riser/build-up.' Does not mention when not to use or provide direct alternatives, but the use case is clear.

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