Skip to main content
Glama

mcp_opendaw_add_anticipation

Add anticipation notes before strong beats to create syncopation. Specify scale, direction, offset, and track to insert early pitch-matching notes for jazz, pop, or Latin feel.

Instructions

Add anticipation notes before strong-beat notes.

Anticipation is the fourth classic non-chord tone technique: a note that arrives early — on the weak part of the beat before a strong beat — anticipating the pitch of the upcoming note. This creates forward rhythmic motion and is ubiquitous in jazz, pop, and Latin music.

Unlike passing tones (which connect two different pitches stepwise), suspensions (which hold a note into the next chord), and neighbor tones (which ornament a single note), anticipation reaches forward to the next melodic/harmonic goal before the beat arrives.

Structure: [original note shortened] → [anticipation on weak beat] → [strong beat note]

The tool finds notes on strong beats (integer beat positions) and inserts an anticipation note just before them. The anticipation has the same pitch as the target note (or a related scale tone if direction is set), placed on the weak portion of the beat.

Jazz syncopation, pop vocal anticipations, salsa montuno, and funk guitar stabs all rely on this device.

Args: unit_index: Audio unit index track_index: Note track index region_index: Region index (-1 = first region) scale: Scale for anticipation pitch selection ("major", "minor", "dorian", "phrygian", "lydian", "mixolydian", "locrian", "harmonic_minor", "melodic_minor", "pentatonic", "blues", "chromatic") root: Root note for scale (C, C#, D, ... B) anticipation_offset: How early the anticipation arrives, in beats before the strong beat (0.0625-0.5, default 0.25 = sixteenth note before). Smaller = more subtle, larger = more pronounced. anticipation_fraction: Duration of anticipation as fraction of the offset gap (0.1-1.0, default 0.33). Controls how long the anticipation note lasts relative to the gap before the strong beat. anticipation_velocity: Velocity of anticipation note (0-1, default 0.55 — softer than the main note, as it is on a weak beat). direction: Anticipation pitch direction — "auto": same pitch as target note (classic anticipation) "upper": one scale step above target "lower": one scale step below target "approach": scale step approaching target from the direction of the previous note min_duration_beats: Minimum note duration in beats to qualify (0.5-4.0, default 1.5). Ensures the target note is long enough to anticipate meaningfully. cross_track: If >= 0, place anticipations on this track index instead of source track (preserves original notes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
scaleNomajor
directionNoauto
unit_indexYes
cross_trackNo
track_indexYes
region_indexNo
min_duration_beatsNo
anticipation_offsetNo
anticipation_fractionNo
anticipation_velocityNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description carries full burden. It discloses the algorithm (finds notes on strong beats, inserts anticipation before them), the structural transformation '[original note shortened] → [anticipation on weak beat] → [strong beat note]', and cross_track behavior that preserves original notes when set. This exceeds typical 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 long but appropriately so for an 11-parameter tool. It is logically structured: definition, comparison, structure, operational summary, genres, and parameter details. Every sentence adds value with no redundancy.

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?

The description covers the musical concept, algorithm behavior, all parameters, genre applicability, and cross-track options. An output schema exists, so not describing return values is acceptable. This is a complete, self-sufficient description.

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 is 0%, yet the description compensates thoroughly by documenting all 11 parameters with ranges, defaults, and musical rationale, e.g., anticipation_offset '0.0625-0.5, default 0.25 = sixteenth note before' and direction options with meanings. No parameter is left unexplained.

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 opening line 'Add anticipation notes before strong-beat notes' is a specific verb+resource statement. The description further distinguishes this from sibling tools like passing tones, suspensions, and neighbor tones, making it unmistakably the anticipation ornament tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly contrasts with 'passing tones (which connect two different pitches stepwise), suspensions (which hold a note into the next chord), and neighbor tones (which ornament a single note)' and names applicable genres (jazz, pop, Latin), providing clear when-to-use context and differentiation from similar 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