Skip to main content
Glama

mcp_opendaw_create_balkan_meter

Creates Balkan additive meter patterns with asymmetric beat groupings (e.g., 2+2+3) and accent structures for tapan drum.

Instructions

Create a Balkan additive meter pattern — asymmetric time signatures with unequal beat groupings.

Balkan music uses "additive" meters: time signatures like 7/8, 9/8, 11/8, 13/8 where the measure is divided into unequal groups of 8th notes. Unlike Western "odd time" (which counts uniformly), Balkan music groups beats into patterns like 2+2+3 (7/8), 2+2+2+3 (9/8), 2+2+3+2+2 (11/8). Each group has a distinct accent pattern, creating the characteristic "limping" feel.

The tapan (large frame drum, similar to daire/def) plays the bass pattern: a low hit at the start of each group, high hits on the internal beats. The accent structure is the defining feature — the groups are not equal, so the listener perceives a lopsided, driving rhythm.

meters: "7_8" — 7/8: groups 2+2+3. The most common Balkan meter. Found in Macedonian, Bulgarian, Greek folk music. Accents on 1, 3, 5. "9_8" — 9/8: groups 2+2+2+3. Used in Bulgarian horo, Greek kalamatianos. Accents on 1, 3, 5, 7. Longer "limp" at the end. "11_16" — 11/16: groups 2+2+3+2+2. Bulgarian krivo horo. Very asymmetric. "13_8" — 13/8: groups 2+2+3+2+2+2. Bulgarian elenino horo. Longest common additive meter. "7_8_sand" — 7/8: groups 3+2+2 (reversed). Sandansko oro, Macedonian. Different accent placement, "backwards" feel. "9_8_ska" — 9/8: groups 2+3+2+2. Deviationska variant.

variations: "classic" — Traditional tapan pattern. Kick on group starts, snare on internal beats, hi-hat on all 8ths. "modern" — Modern Balkan fusion (Shantel, Balkan Beat Box). Kick patterns more syncopated, added ghost snares. "wedding" — Wedding band style. Denser hi-hat, more snare fills, tapan rolls at cycle end.

Args: meter: Meter name (7_8, 9_8, 11_16, 13_8, 7_8_sand, 9_8_ska). cycles: Number of measure cycles (1-32). variation: Pattern variation (classic, modern, wedding). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. kick_pitch: Kick/tapan low MIDI pitch (36 = C1). snare_pitch: Snare/tapan high MIDI pitch (40 = E1). hh_pitch: Hi-hat MIDI pitch (42 = F#1). tapan_pitch: Tapan roll MIDI pitch (45 = A1).

Returns notes created, meter grouping, accent positions, and pattern info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
meterNo7_8
cyclesNo
hh_pitchNo
velocityNo
variationNoclassic
kick_pitchNo
start_beatNo
unit_indexNo
snare_pitchNo
tapan_pitchNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries full burden. It explains the output (notes, grouping, accents) and the tapan pattern, but does not disclose side effects (e.g., whether existing notes are modified, or the interaction with track/unit indices). Constraints like velocity range (0-1) are mentioned, but error conditions are not.

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 well-structured: concept overview, meter listing, variations, then parameter list. Front-loaded with purpose. Slightly verbose with extensive meter background, but appropriate for a specialized creative tool. No wasted sentences.

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?

Given the complexity (11 parameters, output schema exists), the description is fairly complete: it explains the theory, all parameters, and return values. Missing details about DAW state interaction (e.g., whether tracks/units must pre-exist) and validation assumptions, but overall adequate for an informed agent.

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

Parameters4/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. Each parameter has a brief description (e.g., meter names, cycles range, pitch roles), adding meaning beyond type/defaults. Some descriptions (like pitches) could be more detailed, but overall the tool's parameters are adequately explained.

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 the tool creates Balkan additive meter patterns, a specific verb+resource. It distinguishes itself from sibling rhythm tools by focusing on asymmetric time signatures with detailed meter and variation options.

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?

Usage is implied through the description of Balkan meters, but no explicit guidance on when to use this tool versus alternatives like create_cross_rhythm or create_euclidean_rhythm. No when-not-to-use or prerequisite conditions are mentioned.

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