Skip to main content
Glama

mcp_opendaw_create_synthwave_arrangement

Generates a complete synthwave arrangement with retro drums, arpeggiated bass, dreamy pads, and nostalgic lead on four tracks, using the classic i-VI-III-VII progression.

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
Behavior3/5

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

With no annotations, the description carries full transparency weight. It richly details the musical pattern generation (drum hits, arpeggios, chord voicings, BPM range) and mentions return values, but it omits critical operational behaviors such as whether existing notes on the target tracks are cleared, overwritten, or appended, and whether the tracks must pre-exist. This is a notable gap for a DAW mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with a summary and bullet points, but it is verbose and contains redundancy, such as repeating 'fundamental difference' and elaborating on genre distinctions at length. It front-loads the key purpose but would benefit from trimming redundant prose to focus on essentials.

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?

The description is comprehensive for a genre-creation tool: it covers all musical parameters, provides two usage examples, states constraints (bars multiple of 4, BPM range), and describes return values. However, it lacks operational context like track prerequisites and overwrite behavior, and doesn't explain velocity or start_beat, which prevents a perfect score.

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%, but the description compensates by explaining bpm, bars, root, octave, unit_index, and all four track indices with ranges, defaults, and musical rationale. However, velocity and start_beat are absent from the description, leaving those parameters reliant on their self-explanatory names and schema defaults.

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 'Create a full synthwave arrangement — retro drums + arpeggiated bass + dreamy pads + nostalgic lead across 4 tracks,' which is a precise verb+resource+style statement. It also distinguishes itself from sibling arrangement tools by repeatedly contrasting the arpeggiated bass with house, techno, and reggae, making it unmistakable what this tool is for.

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 provides explicit genre differentiation: '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.' It also contrasts synthwave with pop to clarify harmonic context, offering clear guidance on when to choose this tool.

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