Skip to main content
Glama

mcp_opendaw_create_taiko_ensemble

Create a Japanese taiko ensemble with dramatic dynamics, using four percussion instruments and multiple styles for authentic kumi-daiko drumming.

Instructions

Create a Japanese taiko ensemble — kumi-daiko group drumming with dramatic dynamics.

Taiko (literally "fat drum") is Japanese percussion with a history spanning over a millennium. Modern kumi-daiko (group taiko) was created in the 1950s by Daihachi Oguchi, combining multiple drum types into an ensemble. The defining characteristic is dramatic dynamic contrast — from near silence to thunderous power — and the use of silence (ma) as a structural element.

The four core instruments:

  1. ODAIKO — The largest drum. Deep, resonant, thunderous. Plays sparse, powerful hits that mark structural points. The "earthquake" of the ensemble. Very low pitch.

  2. CHU-DAIKO — Medium drum. The workhorse — plays the main rhythmic patterns. Mid-range pitch, full-bodied tone. Most of the notes.

  3. SHIME-DAIKO — Small, high-pitched drum. Plays fast, tight patterns and timekeeping. The "metronome" of the ensemble. High, snappy.

  4. ATARIGANE — Hand gong (metal). Plays accents and calls. Bright, metallic, piercing. Used for dramatic punctuation.

Stroke vocabulary (kakegoe): DON — Loud center hit (chu-daiko, odaiko) KA — Rim hit (shime-daiko) DOKO — Double hit (don-ko) TSU — Soft, muted stroke SU — Silence / rest (ma)

styles: "miyake" — Miyake-style: steady chu-daiko pulse with dramatic odaiko accents. Low stance, powerful, sustained. 4/4 with syncopated odaiko on 2.5 and 4. Shime plays continuous 8th notes. Atarigane calls on bar starts. "yatai" — Yatai-bayashi: festival style. Faster, more joyous. Shime plays 16th notes, chu-daiko alternates don/doko, odaiko on downbeats. Atarigane on offbeats. "edo" — Edo-bayashi: Edo period festival. Steady, march-like. Chu-daiko on 1 and 3, shime on all 8ths, odaiko sparse (only on phrase ends). Atarigane sparse. "hachijo" — Hachijo-style: soloistic, dramatic. Long odaiko rolls with chu-daiko accents. Ma (silence) between phrases. Sparse but powerful. Slow tempo feel. "omega" — Modern taiko (Kodo-style). Dense, aggressive, contemporary. All four instruments at high density. Odaiko on every beat, chu-daiko 16ths, shime 32nd rolls, atarigane accents. Maximum energy.

Args: bars: Pattern length in bars (4-32, even). style: Style name (miyake, yatai, edo, hachijo, omega). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. odaiko_pitch: Odaiko (large drum) MIDI pitch (35 = B0). chu_daiko_pitch: Chu-daiko (medium drum) MIDI pitch (38 = D1). shime_pitch: Shime-daiko (small drum) MIDI pitch (42 = F#1). atarigane_pitch: Atarigane (gong) MIDI pitch (50 = D2).

Returns notes created, instrument breakdown, and style info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
styleNomiyake
velocityNo
start_beatNo
unit_indexNo
shime_pitchNo
track_indexNo
odaiko_pitchNo
atarigane_pitchNo
chu_daiko_pitchNo

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 explains that the tool generates MIDI notes for four instruments with defined pitches and styles, and returns a breakdown. It lacks details on whether it overwrites or appends to existing notes, but covers key behavioral aspects of the generative process.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long and includes historical context that may not be essential for tool usage. While well-structured with instrument, stroke, and style sections, it could be more concise by trimming extraneous cultural background.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, no annotations, no schema descriptions), the description provides substantial context on instruments and styles but lacks clarity on how the generation interacts with existing content (e.g., overwrite vs. append) and the exact role of some parameters like unit_index.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It richly describes styles and pitches (e.g., '35 = B0'), but fails to explain positional parameters like unit_index, track_index, and start_beat. Partial compensation—some parameters are well-documented, others are merely listed.

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 Japanese taiko ensemble (kumi-daiko) with specific instruments and styles. The purpose is unambiguous and distinct from sibling tools like create_djembe_ensemble or create_korean_percussion.

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

Usage Guidelines3/5

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

The description provides extensive cultural and technical context but lacks explicit guidance on when to use this tool versus alternatives. No 'when to use' or 'when not to use' statements, leaving the agent to infer from context.

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