Skip to main content
Glama

mcp_opendaw_create_additive_rhythm

Create additive rhythms from unequal note groupings like 3+2+2 for irregular meters and shifting accents.

Instructions

Create an additive rhythm — unequal groupings within a bar.

The defining technique of Messiaen, Stravinsky, Bartok, Ligeti, and modern math rock / prog metal. Instead of dividing a bar into equal parts (eighth-eighth-eighth-eighth), the bar is divided into unequal groups (3+2+2 = 7 eighths, 2+3+2 = shifting accent, 5+3 = 8 eighths).

The resulting accent pattern creates a sense of irregular meter within a nominal time signature — the pulse "turns" inside the bar.

Examples: create_additive_rhythm("3+2+2", "eighth") -> 7 eighth notes grouped as 3-2-2, accents on notes 1, 4, 6 (Bartok "Bulgarian Rhythm", Math rock 7/8 feel) create_additive_rhythm("2+3+2", "eighth", repeats=4) -> shifting accent pattern, 4 bars create_additive_rhythm("5+3", "eighth", pitch="scale_up") -> 8 eighths in 5+3 grouping, ascending scale create_additive_rhythm("3+2+2", "sixteenth", repeats=2, decay=0.1) -> 7 sixteenths per bar, velocity decay within groups

Args: grouping: Plus-separated group sizes (e.g. "3+2+2", "5+3", "2+1+2"). Each number = count of notes in that group. Sum = total notes per bar. 2-6 groups, 2-16 notes total. unit: Note value — "eighth", "quarter", "sixteenth", "thirty_second". repeats: Number of bars (1-16). pitch: Pitch mode — "root" (same note), "scale_up" (ascending scale), "scale_down" (descending), "alternating" (up/down per note), "octave_bounce" (root->octave->root). scale: Scale for pitch modes (minor, major, dorian, phrygian, etc.). root: Root note (C, C#, D, ...). octave: Base octave (1-6). accent_mode: Where to place accents — "group_start" (first note of each group gets accent), "group_end" (last note), "every_note" (all same velocity). accent_velocity: Velocity for accented notes (0-1). normal_velocity: Velocity for non-accented notes (0-1). decay: Velocity decay within each group (0-0.3). Each subsequent note in a group gets slightly softer. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, grouping structure, accent pattern, and bar layout.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
unitNoeighth
decayNo
pitchNoroot
scaleNominor
octaveNo
repeatsNo
groupingYes
start_beatNo
unit_indexNo
accent_modeNogroup_start
track_indexNo
accent_velocityNo
normal_velocityNo

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 the accent pattern behavior (e.g., 'accents on notes 1, 4, 6'), what parameters affect the output, and states the return value ('Returns notes created, grouping structure, accent pattern, and bar layout'). It doesn't disclose whether existing notes at start_beat are overwritten or merged, which would be useful, but overall it is reasonably transparent.

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 long but well-structured: a concise definition, multiple illustrative examples, then a comprehensive Args list. Each section earns its place, and the front-loaded concept plus examples quickly orient the user. The formatting with line breaks and code-style examples improves readability.

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 complexity (14 parameters, musical concept), the description covers all necessary facets: what it does, how to use it, parameter details, and return values. The presence of an output schema reduces the need to detail returns, but the description still provides an overview. Combined with excellent parameter documentation, it is fully 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%, so the description fully compensates. Every parameter is documented with allowed values, defaults, and examples (e.g., grouping, unit, accent_mode, decay). The examples show how parameters combine to generate specific rhythmic patterns, which goes far beyond the bare schema.

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 'Create an additive rhythm — unequal groupings within a bar,' which clearly states the verb, resource, and core concept. It further distinguishes the tool from other rhythm generators by explaining the specific technique (3+2+2, 5+3) with musical context and examples.

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 gives rich context on when this tool is appropriate (Messiaen, Stravinsky, math rock, Balkan rhythms) and provides multiple examples showing varying parameters. However, it does not explicitly mention alternatives like create_polyrhythm or create_hemiola, nor does it state exclusion criteria, so it falls short of a 5.

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