Skip to main content
Glama

mcp_opendaw_create_ambient_arrangement

Creates a 70 BPM ambient arrangement with sustained pads, drifting melody, minimal percussion, and sub-bass drone for atmospheric soundscapes.

Instructions

Create an ambient arrangement — 70 BPM atmospheric soundscape.

Ambient music (Brian Eno, Stars of the Lid, Aphex Twin Selected Ambient Works) focuses on atmosphere, texture, and sustained sound over rhythm and melody. Key characteristics:

  • 60-80 BPM (or no clear pulse), 4/4 time

  • Long sustained pad notes with slow evolution

  • Sparse, minimal percussion (or none)

  • Drifting melodic fragments, no clear phrase structure

  • Reverb-drenched, wide stereo, cinematic

  • Modal harmony (sustained chords, slow changes)

Creates 4 tracks:

  1. Pad (track_index): Long sustained chord notes (8 bars each), mode-based (major/minor/dorian/lydian), very slow harmonic rhythm. Root, fifth, octave — open voicings.

  2. Melody (track_index+1): Sparse, drifting melodic fragments — long notes (2-4 bars), wide intervals, lots of space. Starts after 8 bars.

  3. Drums (track_index+2): Extremely sparse — single kick on bar 1 of every 8 bars, occasional shaker. Almost subliminal pulse.

  4. Bass (track_index+3): Sustained sub-bass drone, root note only, changes with pad harmony. Very low octave.

Default key: C major (most common ambient key). Default 32 bars for proper ambient evolution length.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
key_rootNoC
velocityNo
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses the arrangement's structural details: track roles, default BPM/keys/bars, and harmonic approach. It does not cover side effects like project state modifications or prerequisites, but the creation behavior is well-documented.

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 detailed but verbose, including a mini-tutorial on ambient music characteristics. While this adds context, it could be more concise for quick agent parsing. The key functionality is front-loaded, but excess text may dilute efficiency.

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 7 parameters and an output schema, the description covers the arrangement's core behavior and defaults. It lacks explanation for three parameters but otherwise provides a solid mental model. The output schema exists, so return value explanation is unnecessary.

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%, but the description explains several parameters (track_index, bars, key_root, bpm) and their defaults. However, velocity, start_beat, and unit_index are not addressed, leaving gaps. The explanation of track_index plus offsets is helpful.

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 ambient arrangement and enumerates the 4 tracks it generates (Pad, Melody, Drums, Bass). It provides specific genre characteristics and default settings, making the purpose immediately clear and distinct from sibling arrangement tools.

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

Usage Guidelines3/5

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

The description implies usage for ambient soundscapes but does not explicitly state when to use this tool over other arrangement creation tools. No direct comparisons or exclusions are provided, though the genre-specific naming helps the agent infer context.

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