Skip to main content
Glama

mcp_opendaw_create_euclidean_rhythm

Distribute onsets evenly across steps to produce Euclidean rhythms like tresillo and samba.

Instructions

Create a Euclidean rhythm — distributes k onsets across n steps as evenly as possible.

The Euclidean algorithm (BJK algorithm) generates most of the world's classic rhythms: E(3,8) = tresillo (Cuban, Arabic, 3-3-2) E(5,8) = cinquillo (Cuban) E(7,16) = samba, rumba E(7,12) = bembé (West African) E(2,5) = tresillo variant E(4,9) = Aksak (Balkan) E(3,7) = Persian/Arabic

onsets: Number of hits (k). 1-32. steps: Total number of steps (n). 2-64. Must be >= onsets. rotation: Rotate the pattern clockwise by N steps. 0 = no rotation. bars: Number of bars to repeat. Each step = one (4/steps)th of a bar. pitch: MIDI pitch for all hits. velocity: Velocity 0-1. Accents (first onset of each group) get +0.15. duration: Note duration in beats.

Returns notes created, pattern as binary string (1=hit, 0=rest), and Euclidean notation E(k,n).

Example: create_euclidean_rhythm(onsets=3, steps=8, track_index=0) # tresillo create_euclidean_rhythm(onsets=7, steps=16, pitch=38, track_index=1) # samba

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
pitchNo
stepsNo
onsetsNo
durationNo
rotationNo
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?

No annotations provided, so description carries full burden. It describes algorithm, parameter effects (e.g., velocity accent), and return values. Lacks disclosure of error handling or edge cases, but overall covers main behavioral aspects.

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?

Front-loaded with purpose and algorithm. Well-structured with examples, parameter list, and return description. Slightly lengthy but information-dense; every sentence adds value.

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?

Covers algorithm, parameter constraints, return format, and examples. Output schema exists but its content is not detailed here. Missing some parameter descriptions and potential error scenarios, but overall complete for a creation tool.

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 has 0% description coverage. Description explains 7 of 10 parameters (onsets, steps, rotation, bars, pitch, velocity, duration) with ranges. Missing descriptions for start_beat, unit_index, track_index. Provides significant added meaning for most parameters.

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?

Description clearly states the tool creates a Euclidean rhythm, explaining the algorithm and listing classic rhythms. It uniquely distinguishes from siblings like create_breakbeat or create_polyrhythm by specifying a precise mathematical method.

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?

Provides examples of when to use specific Euclidean patterns but lacks explicit guidance on when to prefer this tool over alternatives like create_samba_pattern or create_breakbeat. Usage context is implied through examples rather than stated.

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