Skip to main content
Glama

mcp_opendaw_transcribe_drums

Transcribe drum audio into MIDI notes for your DAW track. Detects kick, snare, and hi-hat onsets from WAV files, converts them to a playable MIDI pattern.

Instructions

Transcribe drum onsets from an audio file into MIDI notes on a DAW track.

Audio-to-MIDI drum transcription — converts a drum recording (or any audio with percussive content) into MIDI notes. Pure Python, no external deps.

Pipeline:

  1. Parse WAV file

  2. Split into 3 frequency bands (kick <250Hz, snare 250-2500Hz, hat >2500Hz)

  3. Per-band onset detection (energy spike above local average)

  4. Classify each onset: kick (pitch 36), snare (38), hat (42)

  5. Estimate velocity from onset amplitude

  6. Convert onset times to beat positions (if bpm provided)

  7. Create MIDI notes on the specified track via create_notes_batch

Use cases:

  • Extract a drum groove from a Suno track → reuse as MIDI pattern

  • Transcribe a real drum recording → edit/quantize in DAW

  • Replace original drums with a different instrument

filename: WAV file name (in exports dir) or absolute path. bpm: Tempo for beat conversion (0 = auto-detect via detect_bpm first). sensitivity: Onset detection threshold (1.0=more sensitive, 2.0=less, default 1.5). unit_index: AU index with note tracks. track_index: Track to place transcribed notes.

Returns: notes created, onset count, band counts (kick/snare/hat), bpm, duration.

Example:

Transcribe a drum loop from a downloaded Suno track

result = transcribe_drums("suno_track.wav", bpm=120)

Auto-detect BPM first

result = transcribe_drums("drum_loop.wav") # bpm=0 → auto-detect

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
filenameYes
unit_indexNo
sensitivityNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so admirably. It discloses the entire processing pipeline (frequency bands, onset detection, pitch mapping, velocity estimation), the use of create_notes_batch for note creation, and the return values. It even explains the sensitivity threshold semantics.

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 with a summary, numbered pipeline, use cases, parameter list, return values, and an example. It is long but every section adds value, and the front-loaded purpose ensures quick comprehension.

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 audio transcription tool with no annotations, the description covers input format, algorithm details, parameter semantics, return values, and examples. It leaves no critical gap and even provides practical usage context for integration.

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%, so the description must compensate fully. It explains every parameter in plain language: filename (path semantics), bpm (0=auto-detect), sensitivity (range and default), unit_index, and track_index. This goes far beyond the schema's type/default info.

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 opens with a specific verb+resource statement: 'Transcribe drum onsets from an audio file into MIDI notes on a DAW track.' It clearly distinguishes this from siblings like transcribe_melody and transcribe_audio by focusing on drum onsets, and the pipeline and use cases reinforce the specific scope.

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 concrete use cases (extract drum groove, transcribe recording, replace drums) and explicitly references detect_bpm as a prerequisite for auto-detection. It implies when to use this tool, though it lacks an explicit 'when not to use' or named alternative for non-drum audio.

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-ai/opendaw-mcp'

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