Skip to main content
Glama

mcp_opendaw_create_arabic_percussion

Creates an Arabic percussion ensemble with darbuka, daf, and zills, supporting rhythms like maqsum and baladi with customizable bars, velocity, and MIDI pitches.

Instructions

Create an Arabic/Middle Eastern percussion ensemble — darbuka, daf, and zills.

Middle Eastern percussion is built on the interplay between the darbuka (tabla, goblet drum) playing the core rhythm with dum (low) and tek/ka (high) strokes, the daf (frame drum) providing sustained resonance and rolls, and zills (sagat, finger cymbals) adding shimmering accents. The rhythms are cyclical with distinctive asymmetry — maqsum has a characteristic gap between dum strokes that creates tension.

The stroke vocabulary: DUM — Low, resonant center stroke on darbuka (bass register) TEK — High, ringing rim stroke (right hand, accented) KA — High, snapping rim stroke (left hand, lighter) SLAP — Sharp, accented stroke (mid register)

rhythms: "maqsum" — The most common Arabic rhythm: D-T- -T-D- -T-. 4/4, 8 beats. Dum on 1 and 4.5, tek on 2, 3, 5.5, 7. The "mother of all Arabic rhythms". Used in almost all Arabic pop, classical, and folk music. "baladi" — Urban Egyptian version of maqsum: D-D- -T-D- -T-. Dum on 1 and 1.5 (double dum), tek on 3, 5.5, 7. Heavier, more driving. The "baladi groove" of Cairo. "saidi" — Upper Egyptian rhythm: D-T- -T-D-D- -T-. 4/4. Dum on 1, 4.5, and 5 (double dum). Tek on 2, 3, 6.5, 7. From the Said region. Used in Saidi dance and music. "ayoub" — 2/4 cyclical rhythm: D- -T- -D-D-. 4 beats. Dum on 1, 3, 3.5. Tek on 2. Used in Sufi trance, zar ceremonies, and religious processions. "malfouf" — 2/4 fast rhythm: D- -T- -T-. 3 beats. Dum on 1, tek on 2, 2.5. Used in fast entrances, processions, and folk dances. "Running" feel. "chiftetelli" — 8/4 slow rhythm: D- -T- -T- -D- -T-. 8 beats. Dum on 1 and 5.5, tek on 2.5, 3.5, 7.5. Used in Turkish and Greek music, belly dance slow sections.

Args: bars: Pattern length in bars (2-16, even). rhythm: Rhythm name (maqsum, baladi, saidi, ayoub, malfouf, chiftetelli). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. darbuka_pitch: Darbuka MIDI pitch (36 = C1). daf_pitch: Daf (frame drum) MIDI pitch (42 = F#1). zills_pitch: Zills (finger cymbals) MIDI pitch (50 = D2).

Returns notes created, instrument breakdown, stroke types, and rhythm info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
rhythmNomaqsum
velocityNo
daf_pitchNo
start_beatNo
unit_indexNo
track_indexNo
zills_pitchNo
darbuka_pitchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the tool returns notes, an instrument breakdown, stroke types, and rhythm info. It also explains the instruments and stroke mappings, providing moderate transparency. However, it does not explicitly state whether notes are added to an existing track or if there are side effects, though the parameters (unit_index, track_index, start_beat) imply placement.

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 front-loaded with the purpose sentence, but it is lengthy due to extensive educational material on Arabic percussion. While well-structured (purpose, background, stroke types, rhythms, args), it could be more concise without losing essential information. The educational content is valuable but adds verbosity.

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 tool's cultural complexity and 9 parameters, the description is highly complete. It covers all parameters, explains stroke vocabulary and rhythms in detail, and mentions return values. The output schema exists (though not shown), so the description's lack of return format detail is acceptable. No gaps remain for the intended use case.

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 includes an 'Args' section that lists and explains all 9 parameters with brief, meaningful descriptions (e.g., 'bars: Pattern length in bars (2-16, even).'). This adds substantial meaning beyond the bare schema, compensating fully for the coverage gap.

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 starts with a clear, specific verb and resource: 'Create an Arabic/Middle Eastern percussion ensemble.' This immediately distinguishes it from sibling tools like create_djembe_ensemble (African) or create_taiko_ensemble (Japanese), as well as generic create_drum_pattern.

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 does not explicitly state when to use this tool versus alternatives, but the rich educational content about Arabic rhythms, instruments, and stroke vocabulary provides clear context for when this tool is appropriate. It implicitly guides the agent toward Middle Eastern music creation without specifying exclusions.

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