Skip to main content
Glama

mcp_opendaw_create_stutter

Generates a stutter edit pattern—rapid, evolving note repetitions—for build-ups, glitch fills, and vocal chops. Control rate, acceleration, accents, velocity ramp, pitch jitter, and gate.

Instructions

Create a stutter edit — rapid rhythmic repetitions with evolving rate and dynamics.

The classic stutter edit (BT, Imogen Heap, Deadmau5, Skrillex): take a note and repeat it with changing rhythmic density. Unlike create_chop (equal segments) or create_trill (alternating two notes), stutter edit evolves over time — accelerating, decelerating, or shifting accents. Essential for:

  • Build-up transitions before drops

  • Glitch fills at end of phrases

  • Vocal-chop style rhythmic patterns

  • Energy ramps in EDM/hip-hop

pitches: Comma-separated MIDI pitches (1-8, default "60"). Cycles through if repeat_count > len. rate: Base rhythmic subdivision — "16th" (0.25 beats), "32nd" (0.125), "64th" (0.0625), "triplet" (0.167), "triplet32" (0.083). pattern: How rate evolves — "constant" (same spacing throughout), "accelerate" (notes get closer — classic stutter build), "decelerate" (notes spread out — reverse stutter), "ping_pong" (alternate fast/slow), "random" (jittered spacing, seeded). repeat_count: Total repetitions (4-64, default 16). accent_pattern: Velocity accent structure — "none" (all equal), "downbeat" (every 4th accented), "1_and" (1st + 3rd accented), "1_e_and_a" (1st strongest, 3rd medium), "every_other" (alternating accent). velocity_ramp: Dynamic envelope — "constant", "fade_in", "fade_out", "fade_in_out", "build" (exponential increase). gate: Portion of each step with sound (0.3-1.0, default 0.85). Lower = more gaps = choppy. pitch_jitter: Random pitch variation in semitones (0-12, default 0). 0 = exact repeat. unit_index: AU index with note track (-1 = auto-find). track_index: Note track index. start_beat: Position in beats. velocity: Base velocity (0-1). seed: Random seed.

Returns notes created, pattern, rate, total length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
gateNo
rateNo16th
seedNo
patternNoaccelerate
pitchesNo60
velocityNo
start_beatNo
unit_indexNo
track_indexNo
pitch_jitterNo
repeat_countNo
velocity_rampNobuild
accent_patternNodownbeat

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 the full burden and succeeds: it explains the algorithmic behavior (rate evolution patterns, accent structures, velocity ramps, gate, pitch jitter), and discloses that it uses a seeded random generator for reproducibility. It also describes return values, so the agent knows what to expect.

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 every sentence earns its place. It is front-loaded with a one-line purpose, then context, then a structured parameter list. The line breaks and bullet lists make it easily scannable despite the length.

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?

All 13 parameters are fully explained, usage context is given, and return values are specified. The description is completely self-sufficient given the abundant defaults and the output schema note.

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%, but the description compensates thoroughly by documenting each of the 13 parameters with plain-language meaning, valid ranges, defaults, and musical intent. It adds meaning far beyond the schema's type/default definitions.

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 a precise verb+resource: 'Create a stutter edit' and defines it as 'rapid rhythmic repetitions with evolving rate and dynamics.' It distinguishes from sibling tools by explicitly contrasting with create_chop and create_trill, and lists specific musical use cases.

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?

The description gives explicit when-to-use guidance: 'Unlike create_chop... or create_trill... stutter edit evolves over time' and includes a bulleted list of essential use cases (build-up transitions, glitch fills, vocal-chop patterns, energy ramps). This clearly directs the agent to choose this tool over alternatives.

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