Skip to main content
Glama

mcp_opendaw_create_arpeggiated_progression

Generate synthwave, trance, or house arpeggiated chord progressions from a simple chord string. Cycle through chord tones with up, down, updown, random, or bass patterns.

Instructions

Create an arpeggiated chord progression — synthwave/trance arp engine.

Takes a chord progression string (same format as create_chord_pads: "Am-F-C-G") and generates arpeggiated notes cycling through chord tones. This is the synthwave arpeggiated bass, the trance supersaw arp, the house plucked chord stab — all from a simple progression string.

Unlike create_arpeggio (which takes a single chord), this cycles through a full progression, changing chord tones every bars_per_chord bars.

progression: Hyphen-separated chords (same as create_chord_pads). "Am-F-C-G" = i-VI-III-VII in A minor. "C-G-Am-F" = I-V-vi-IV in C major (pop).

pattern: Arpeggio pattern: "up" — root, third, fifth, root(oct) — classic synthwave "down" — oct root, fifth, third, root — descending "updown" — root, third, fifth, oct, fifth, third — full cycle "random" — random chord tones — dreamy, unpredictable "bass" — root only, 8th notes — driving bass arp (synthwave bass)

bars_per_chord: Bars per chord (default 4). octave: MIDI octave (3 = bass arp, 4 = mid arp, 5 = lead arp). velocity: Note velocity (0-1). step_duration: Note length in beats (0.25 = 16th, 0.5 = 8th, 0.125 = 32nd). track_index: Track for arp notes (typically melody track = 3).

Returns chords arpeggiated, total notes, pattern used.

Example:

Synthwave bass arp (16th notes, octave 2)

create_arpeggiated_progression("Am-F-C-G", pattern="bass", octave=2, step_duration=0.25, track_index=1)

Trance supersaw arp (16th up, octave 4)

create_arpeggiated_progression("Fm-Db-Ab-Eb", pattern="up", octave=4, step_duration=0.25, track_index=3)

Pop arp (8th updown, octave 5)

create_arpeggiated_progression("C-G-Am-F", pattern="updown", octave=5, step_duration=0.5, track_index=3)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
octaveNo
patternNoup
velocityNo
start_beatNo
unit_indexNo
progressionNoAm-F-C-G
track_indexNo
step_durationNo
bars_per_chordNo

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. Explains arpeggio generation, pattern cycling, and return values (chords, total notes, pattern). Does not mention side effects or limitations, but behavior is well-described.

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 purpose statement, parameter descriptions, and examples. Reasonably concise for the level of detail, though some genre names repeat.

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?

Given 9 parameters, no annotations, and output schema exists, the description covers essential aspects: parameter explanations, examples, sibling differentiation. Return values are mentioned. Lacks details on start_beat and unit_index.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so description must compensate. Describes key parameters (progression, pattern, octave, velocity, step_duration, track_index) with examples and allowed values. However, start_beat and unit_index are omitted, leaving gaps.

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 an arpeggiated chord progression and distinguishes it from create_arpeggio (single chord vs. full progression). Specific verb 'create' and resource 'arpeggiated chord progression' are used.

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?

Explicitly contrasts with create_arpeggio and gives genre-specific examples (synthwave, trance, house, pop). Provides clear context for when to use, though lacks explicit 'when not to use' guidance.

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