Skip to main content
Glama

mcp_opendaw_create_isorhythm

Create isorhythmic patterns: a repeating rhythm (talea) and pitch series (color) cycle independently. Set lengths and repeats to generate ever-shifting musical relationships.

Instructions

Create an isorhythm — repeating rhythm (talea) × repeating pitch series (color).

Isorhythm separates rhythm and pitch into two independent cycles. The talea (rhythmic pattern) and color (pitch series) repeat independently, creating constantly shifting relationships as they go in and out of phase. When talea and color have different lengths, the pattern doesn't fully repeat until the least common multiple of both lengths.

Found in medieval motets (Machaut), and heavily influenced 20th-century composers — Messiaen, Boulez, Stockhausen. Distinct from ostinato, which repeats rhythm and pitch together as one unit.

talea: Comma-separated note durations in beats (the repeating rhythm). e.g. "1,1,0.5,0.5,1" = quarter, quarter, eighth, eighth, quarter. color: Comma-separated MIDI pitches (the repeating pitch series). e.g. "60,62,64,65" = C,D,E,F cycling independently of rhythm. repeats: Number of full talea cycles (1-16, default 3). velocity: Velocity of all notes (0-1, default 0.7). unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the isorhythm begins.

Returns notes created, talea/color lengths, phase cycle length, total duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
colorNo60,62,64,65,67,65,64,62
taleaNo1,1,0.5,0.5,1,0.5,0.5,1
repeatsNo
velocityNo
start_beatNo
unit_indexNo
track_indexNo

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 full behavioral burden. It thoroughly explains the independent cycling of talea and color, the least-common-multiple repetition, and the effect of parameters like repeats and start_beat. It also summarizes return values. A minor gap is not explicitly stating whether existing notes are replaced or appended.

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 longer than typical, but well-structured with paragraphs and line breaks. It is front-loaded with the core definition, uses examples efficiently, and the historical context adds richness without excess verbiage.

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 of the isorhythm concept and the fully optional parameters, the description covers the algorithm, all parameters, and output summary. An output schema is present, reducing the need to detail return values. The description provides sufficient context for correct selection and invocation.

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?

The input schema has 0% description coverage, so the description fully compensates by defining every parameter with examples and ranges. For instance, talea and color get comma-separated format examples, and unit_index gets special '-1 = find first AU with note tracks' semantics.

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 isorhythm — repeating rhythm (talea) × repeating pitch series (color),' clearly stating the verb and resource. It also distinguishes the tool from ostinato, which is a direct alternative, by explaining that ostinato repeats rhythm and pitch together.

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 explains the musical concept and explicitly contrasts with ostinato: 'Distinct from ostinato, which repeats rhythm and pitch together as one unit.' This gives a clear alternative and exclusion, though it doesn't enumerate all sibling rhythm tools.

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