Skip to main content
Glama

mcp_opendaw_create_metric_modulation

Create a metric modulation that changes tempo while keeping a note value duration equivalent, using note values or a ratio to compute the new BPM.

Instructions

Create a metric modulation — tempo change that preserves a note-value equivalence.

The defining technique of Elliott Carter, Aaron Copland, John Adams, and progressive rock (Dream Theater, Tool). Unlike a simple tempo change, metric modulation establishes a precise relationship: a specific note value in the new tempo has the same duration as a different note value in the old tempo. The listener perceives a new pulse while the rhythmic fabric remains continuous.

Formula: new_bpm = old_bpm × (new_note_value / old_note_value)

Supported note values:

  • "whole", "half", "dotted_half", "quarter", "dotted_quarter"

  • "quarter_triplet", "eighth", "dotted_eighth", "eighth_triplet"

  • "sixteenth", "dotted_sixteenth", "thirty_second"

Alternatively, pass a ratio like "3:2" (new tempo = 3/2 of old) or "2:3" (new = 2/3 of old) to express the modulation as a simple proportion.

Examples: create_metric_modulation(32, "quarter", "dotted_eighth", old_bpm=120) → new_bpm = 120 × (3/16) / (1/4) = 90 BPM. A dotted eighth at 90 lasts the same as a quarter at 120. create_metric_modulation(16, ratio="3:2", old_bpm=100) → new_bpm = 150. Three notes in new tempo = two in old. create_metric_modulation(48, "eighth", "quarter", old_bpm=140) → new_bpm = 280. Quarter at new tempo = eighth at old (doubling).

Args: position_beats: Beat position where modulation occurs. old_note: Note value in the old tempo (default "quarter"). new_note: Note value in the new tempo that equals old_note's duration (default "dotted_eighth" — classic Carter modulation). old_bpm: Current BPM. If 0, reads from the project's tempo track. ratio: Direct ratio "N:M" — new_bpm = old_bpm × N/M. Overrides old_note/new_note if provided. add_time_signature: Optional new time signature as "N/D" (e.g. "3/4", "6/8"). If provided, also creates a time signature change event at the same position.

Returns old_bpm, new_bpm, ratio, equivalence, and events created.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ratioNo
old_bpmNo
new_noteNodotted_eighth
old_noteNoquarter
position_beatsYes
add_time_signatureNo

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 covers behavior: it creates tempo modulation events, returns old/new BPM, ratio, equivalence, and events. It includes the formula and note values. However, it does not disclose potential side effects, permissions needed, or whether it modifies existing tempo events. Still, it provides substantial transparency.

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 well-structured: starts with purpose, then formula, note values, ratio alternative, examples, and parameter list. It is front-loaded and every sentence provides useful information without repetition. It is detailed yet efficiently organized.

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 6 parameters, 0% schema coverage, and an output schema, the description is exceptionally complete. It covers what the tool does, how to use it, all parameters with defaults, examples, and return values. It also contextualizes the tool within music theory and contrasts with simple tempo changes. No gaps are apparent.

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 must compensate. It thoroughly explains all 6 parameters: position_beats, old_note, new_note, old_bpm, ratio, add_time_signature, including defaults, meanings, and examples. It also lists supported note values and describes the ratio option. This adds immense value 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 clearly states the tool creates a metric modulation, a tempo change preserving note-value equivalence. It provides the formula, supported note values, and examples, distinguishing it from sibling tools like add_tempo_change or set_bpm.

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 metric modulation with simple tempo changes, implying when to use it. It explains the precise relationship and gives examples, but does not explicitly list when not to use or mention alternatives. The context is clear but lacks explicit exclusions.

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