Skip to main content
Glama

mcp_opendaw_create_korean_percussion

Create a Korean traditional percussion ensemble with janggu, buk, kkwaenggwari, and jing representing weather elements. Choose from styles like nongak, samul_nori, binari, and more.

Instructions

Create a Korean traditional percussion ensemble — nongak (farmers' music).

Korean percussion (samul nori / nongak) uses four instruments representing weather elements:

  1. JANGGU — Hourglass drum with two heads: chwe (left, low, deep) and kyeongbang (right, high, sharp). The most versatile Korean drum. Plays complex interlocking patterns with both hands simultaneously.

  2. BUK — Barrel drum. Deep bass tone. Plays steady downbeats.

  3. KKWAENGGWARI — Small hand gong. High, piercing metallic. The lead instrument — player (sangsoe) calls patterns and signals changes.

  4. JING — Large gong. Deep, resonant, sustained. Plays sparse accents to mark phrase boundaries.

The four instruments represent: janggu = rain, buk = clouds, kkwaenggwari = thunder, jing = wind (lightning in some traditions).

styles: "nongak" — Farmers' music (rural tradition). Steady, driving. Janggu plays the basic nanajanggu pattern (alternating chwe/kyeong on 8th grid). Buk on downbeats. Kkwaenggwari on offbeats with accented calls. Jing on phrase starts. "samul_nori" — Modern stage version (1978, Kim Duk-soo). Faster, denser, more dramatic. Janggu plays 16th patterns with ghost notes. Kkwaenggwari has call-and-response. "binari" — Ritual/shaman opening piece. Slow, ceremonial. Long jing resonance. Sparse janggu. Kkwaenggwari calls. Builds from near silence. "utdari_pungnyu" — Court music style (upper register). Elegant, refined. Buk steady, janggu delicate 8ths, kkwaenggwari sparse. Jing on every 4 bars. "yeongnam_folk" — Yeongnam region folk style (Gyeongsang). Rough, energetic. Buk on 1+3, janggu syncopated, kkwaenggwari dense. Working-class feel.

Args: bars: Pattern length (4-32, even). style: Style name (nongak, samul_nori, binari, utdari_pungnyu, yeongnam_folk). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. janggu_chwe_pitch: Janggu left head (low) MIDI pitch (35 = B0). janggu_kyong_pitch: Janggu right head (high) MIDI pitch (42 = F#1). buk_pitch: Buk (barrel drum) MIDI pitch (36 = C1). kkwaenggwari_pitch: Kkwaenggwari (small gong) MIDI pitch (54 = G#1). jing_pitch: Jing (large gong) MIDI pitch (48 = C2).

Returns notes created, instrument breakdown, and style info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
styleNonongak
velocityNo
buk_pitchNo
jing_pitchNo
start_beatNo
unit_indexNo
track_indexNo
janggu_chwe_pitchNo
janggu_kyong_pitchNo
kkwaenggwari_pitchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description carries full burden. It explains the instrument roles, stylistic patterns, and output (notes, breakdown, style info). It does not disclose potential destructive actions or permissions, but the mutation is well-scoped.

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 lengthy but well-structured with instrument descriptions, style definitions, and parameter list. Each section adds value, though minor redundancy could be trimmed.

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

Completeness4/5

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

With high parameter count, no annotations, and output schema present, the description covers instruments, styles, and parameter semantics. It could mention time signature assumptions or how bars relate to beat count, but overall it is sufficiently complete.

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 lists all 11 parameters with detailed explanations (e.g., MIDI pitch mappings, instrument roles). This fully compensates for the schema's lack of descriptions.

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 Korean traditional percussion ensemble (nongak/samul nori). It distinguishes from sibling tools like create_taiko_ensemble by specifying Korean instruments and styles.

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 does not explicitly state when to use this tool over alternatives. While the cultural context is clear, no guidance is given on prerequisites or scenarios where other percussion tools would be more appropriate.

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