Skip to main content
Glama

mcp_opendaw_create_tuplet_group

Divide a time span into an irrational number of equal parts to create rhythmic tension, such as triplets or septuplets, with full control over pitch, accents, and rests.

Instructions

Create a tuplet group — irrational rhythm subdivision within a time span.

A tuplet divides a time span into N equal parts instead of the normal subdivision. Triplets (3 in 2), quintuplets (5 in 4), septuplets (7 in 4) create rhythmic tension by violating the expected duple meter.

Unlike polyrhythm (multiple voices with different periods) or additive rhythm (unequal groupings), tuplets subdivide a single time span into an irrational number of equal parts — creating a "squeezed" or "stretched" feel within one voice.

Common tuplets: 3 in 2 — triplet (most common, jazz swing, Irish jigs) 5 in 4 — quintuplet (Chopin, Ligeti, modern jazz) 7 in 4 — septuplet (Ferneyhough, new complexity) 11 in 4 — undecuplet (extreme irrational meter) 2 in 3 — duplet (2 notes in triplet space, compound meter)

Args: root: Root note name (C, C#, D, ...). scale: Scale name (major, minor, dorian, etc.). tuplet_number: Number of notes to fit in the span (2-16). 3=triplet, 5=quintuplet, 7=septuplet, etc. span_beats: Time span in beats that the tuplet occupies (0.25-8.0). 1.0 = quarter note span, 2.0 = half note span. base_division: The normal subdivision the tuplet replaces (1-8). 2 = duplet (normal), so triplet = 3 in 2. 4 = sixteenths, so quintuplet = 5 in 4. repeats: Number of times the tuplet repeats (1-16). octave: Starting MIDI octave (1-6). pitch_mode: Pitch assignment mode (scale_asc, scale_desc, chord, repeated, alternating). rest_positions: Comma-separated tuplet positions that are rests (0-indexed). E.g., "2,4" = positions 2 and 4 are rests. velocity: Base velocity 0-1. accent_first: If True, first note of each tuplet gets accent. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, tuplet ratio, and timing info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
scaleNomajor
octaveNo
repeatsNo
velocityNo
pitch_modeNoscale_asc
span_beatsNo
start_beatNo
unit_indexNo
track_indexNo
accent_firstNo
base_divisionNo
tuplet_numberNo
rest_positionsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided. The description explains the concept and parameters, and mentions return values (notes, ratio, timing). However, it does not explicitly state that the tool adds notes to a track or disclose side effects, permissions, or constraints, which would be needed for full transparency.

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 purpose and concept, followed by a structured Args list. It is slightly verbose but each sentence serves a purpose. Could be trimmed slightly but well-organized.

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?

The description covers the concept, parameter details, common tuplets, and return value. It is complete enough for a creation tool with an output schema. Minor gaps include error conditions and explicit mention of additive behavior to existing tracks.

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%, but the description provides detailed explanations for key parameters (tuplet_number, span_beats, base_division, rest_positions, etc.) with examples and ranges. Some generic parameters like root, scale, and velocity are not elaborated, but overall adds significant meaning beyond the 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 clearly states 'Create a tuplet group — irrational rhythm subdivision within a time span.' It uses a specific verb and resource, and contrasts with polyrhythm and additive rhythm, distinguishing it from sibling tools.

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 contrasts tuplets with polyrhythm and additive rhythm, and lists common tuplets with usage contexts (jazz swing, Chopin, etc.). It provides clear context but lacks explicit when-not-to-use or alternatives beyond the contrasts.

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