Skip to main content
Glama

mcp_opendaw_create_synthwave_arrangement

Generate a complete synthwave arrangement: retro drums, arpeggiated bass, dreamy pads, and nostalgic lead. Uses the classic i-VI-III-VII minor progression for 80s-inspired sound.

Instructions

Create a full synthwave arrangement — retro drums + arpeggiated bass + dreamy pads + nostalgic lead across 4 tracks.

80s-inspired synthwave with the signature nostalgic feel — fundamentally different from other electronic genres:

  • Track 0: Drums — retro four-on-floor: kick on every quarter (softer than house), snare on beats 2 & 4, closed hats on all 8ths. The classic 80s drum machine feel — driving but not aggressive, nostalgic not punchy.

  • Track 1: Bass — ARPEGGIATED 16th notes: the engine of synthwave. Root → octave → fifth → octave pattern, driving and relentless. Not sustained like reggae, not sub-drone like techno — arpeggiated movement.

  • Track 2: Pads — sustained minor chords, full bar length. Dreamy, long release, filling the harmonic space. The nostalgic wash underneath.

  • Track 3: Lead — simple nostalgic melody following chord changes, with echo-like call-and-response. Memorable phrases that breathe.

Uses the classic synthwave progression i-VI-III-VII (Am-F-C-G in A minor) — the four chords that define the genre. Different from pop's I-V-vi-IV (same chords, different order and tonal centre — synthwave is minor-key, pop is major).

At 110 BPM (default), this creates the classic synthwave groove — mid-tempo, nostalgic, driving. The arpeggiated bass is the fundamental difference from all 11 other arrangements: house has off-beat stabs, techno has sub drones, synthwave has relentless 16th-note arpeggios.

bpm: Tempo (90-130, default 110 = classic synthwave). bars: Arrangement length (4-16, default 8). Must be multiple of 4 for chord cycle. root: Root note (A is the classic synthwave key — Am). octave: MIDI octave for bass (2 = A2=45, standard synthwave bass register). unit_index: AU index with note tracks. drum_track / bass_track / pad_track / lead_track: Track indices.

Returns notes created per track and total.

Example: create_synthwave_arrangement(bpm=110, root="A", bars=8) create_synthwave_arrangement(bpm=100, root="D", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoA
octaveNo
velocityNo
pad_trackNo
bass_trackNo
drum_trackNo
lead_trackNo
start_beatNo
unit_indexNo

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 fully carries the burden. It provides extensive detail on each track's role, the chord progression (i-VI-III-VII), tempo range (90-130 BPM, default 110), key (A minor), and the driving 16th-note arpeggio pattern. It does not disclose potential performance impacts or error handling, but the level of detail is high.

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?

The description is lengthy but well-structured with bullet points for each track and a clear parameter summary. It front-loads the purpose, then details each track's role, chord progression, and tempo. Every sentence adds value, though it could be slightly more concise.

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 the complexity (11 parameters, no annotations, with output schema), the description is highly complete. It explains the genre, arrangement structure, chord progression, parameter constraints, and provides examples. It does not cover error conditions or return format (output schema exists), but overall very thorough.

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

Parameters4/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 explains bpm (range 90-130), bars (4-16, multiple of 4), root (default A), octave (default 2), and the track indices (drum_track, bass_track, etc.) including defaults. Some parameters like velocity and start_beat are only mentioned in passing, but most are covered.

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 'Create a full synthwave arrangement' and details the four tracks with specific characteristics (retro drums, arpeggiated bass, dreamy pads, nostalgic lead). It distinguishes from sibling genre arrangement tools by explicitly contrasting synthwave's arpeggiated bass with house off-beat stabs and techno sub-drones.

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 provides clear context for when to use this tool (when creating a synthwave-style arrangement) and contrasts it with other electronic genres (house, techno, reggae) by highlighting the unique arpeggiated bass. It does not explicitly state when not to use it, but the comparisons serve as implicit 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