Skip to main content
Glama

mcp_opendaw_extract_rhythm

Extract rhythmic patterns from note regions, including onset grids, syncopation scores, inter-onset intervals, and rhythm density. Use to analyze groove or compare rhythms.

Instructions

Extract rhythmic pattern from notes — onset grid, syncopation, IOI.

Returns a rhythmic analysis of notes in a region:

  • Onset grid: binary pattern showing which grid positions have note onsets

  • Inter-onset intervals (IOI): time between consecutive note starts

  • Syncopation score: how much the rhythm emphasises weak beats (0-1)

  • Rhythm density: fraction of grid positions with onsets

  • Rhythm string: compact representation (x=onset, .=rest)

  • Swing factor: ratio of odd vs even 16th positions

Grid resolutions:

  • "16th" — 16 positions per bar (default, most common)

  • "8th" — 8 positions per bar

  • "32nd" — 32 positions per bar (fine detail)

  • "quarter" — 4 positions per bar (coarse)

Useful for:

  • Understanding a rhythm before cloning it to another track

  • Measuring syncopation (high = funky, low = straight)

  • Extracting groove for groove_transfer

  • Comparing rhythms between sections

  • Feeding rhythm to generate_melody (rhythm param)

unit_index: AU index. track_index: Note track index. region_index: Region (-1 = first region). grid: Grid resolution (16th/8th/32nd/quarter).

Returns rhythm analysis.

Example: rhythm = extract_rhythm(0, 0, grid="16th")

onset_grid, syncopation, ioi, rhythm_string

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gridNo16th
unit_indexYes
track_indexYes
region_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations provided, so description carries full burden. It lists all returned metrics (onset grid, IOI, syncopation, density, rhythm string, swing factor) and explains grid resolutions. No hidden side effects.

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?

Well-structured with summary, return fields, grid resolutions, use cases, and parameter list. Slightly long but efficient; no fluff.

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?

Output schema exists but description compensates with clear return value descriptions. Covers enough for agent to use correctly without external reference.

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 coverage 0%, but description fully documents all 4 parameters: unit_index, track_index, region_index (with default -1), and grid (with enumerated values and defaults). Adds meaning beyond 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?

Clear verb+resource: 'Extract rhythmic pattern from notes'. Distinguishes from siblings like groove_transfer or harmonic rhythm analysis by focusing on rhythm parameters.

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?

Provides explicit use cases (cloning, syncopation measurement, groove transfer, comparison, melody generation). Does not state when not to use, but context is clear given sibling 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-team/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server