Skip to main content
Glama

mcp_opendaw_create_country_arrangement

Generates a complete country arrangement with boom-chick guitar, root-five bass, drums, and major pentatonic fiddle lead in a I-IV-V progression.

Instructions

Create a full country arrangement — boom-chick guitar + root-five bass + major pentatonic fiddle lead.

Classic country/Americana — the foundation of American roots music:

  • Track 0: Drums — straight 8th backbeat: kick on 1 and 3, snare on 2 and 4, steady 8th hi-hats. Country drums are straight, not shuffled like blues — the groove comes from the guitar, not the drums.

  • Track 1: Bass — root-five pattern: root on beat 1, fifth on beat 3. The classic country bass — simple, steady, and unmistakable.

  • Track 2: Chords — boom-chick guitar: alternating bass note (beat 1) + chord strum (beat 2), bass note (beat 3) + chord strum (beat 4). Triads, not 7ths — country harmony is cleaner than blues. The boom-chick is the Carter Family/Johnny Cash pattern.

  • Track 3: Lead — major pentatonic (root, 2, 3, 5, 6) with occasional blue notes (b3, b7). Fiddle-style: long sustained notes, fast scale runs, and bends. The crying fiddle quality.

At 120 BPM (default), this is a classic country two-step tempo. At 90 BPM, it's a country ballad. At 140, it's a fast bluegrass breakdown feel.

The I-IV-V progression: I-I-IV-I-V-I-IV-I (8 bars). Simple, direct, and the backbone of country, folk, and Americana.

bpm: Tempo (80-160, default 120 = classic country two-step). bars: Arrangement length (must be multiple of 8, default 8). root: Root note (G is the most common country key — guitar/capo friendly). octave: MIDI octave for bass (2 = G2=43, standard country bass register). unit_index: AU index with note tracks. drum_track / bass_track / chord_track / lead_track: Track indices.

Returns notes created per track and total.

Example: create_country_arrangement(bpm=120, root="G", bars=8) create_country_arrangement(bpm=90, root="D", bars=16) # ballad, 2 verses

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoG
octaveNo
velocityNo
bass_trackNo
drum_trackNo
lead_trackNo
start_beatNo
unit_indexNo
chord_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations provided, the description must disclose behavioral traits. It describes the generated arrangement structure and mentions return values ('Returns notes created per track and total'), but does not clarify side effects like overwriting existing data, prerequisites (e.g., existing tracks), or system interactions beyond note creation.

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 lengthy but well-structured, starting with a concise purpose then detailing tracks and parameters. Some redundancy exists (e.g., repeating tempo adjustments), and the level of detail may be excessive for a simple creation tool, but it remains organized.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the 11-parameter complexity and no annotations, the description covers the musical output thoroughly—track roles, progression, tempo suggestions. However, it omits system-level context (e.g., whether it creates new tracks or modifies existing ones) and does not leverage the existing output schema to explain return structure.

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 carries the full burden. It explains most parameters (bpm, bars, root, octave, track indices) with specific details like range and defaults. However, velocity, start_beat, and unit_index are not explicitly described, leaving some ambiguity.

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's purpose: 'Create a full country arrangement — boom-chick guitar + root-five bass + major pentatonic fiddle lead.' It specifies the genre and instrumentation, effectively distinguishing it from sibling genre-specific arrangement tools like create_rock_arrangement and create_blues_arrangement.

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 context through genre details but does not explicitly state when to use this tool over alternatives or provide when-not-to-use guidance. It assumes the agent will infer from the genre focus, but lacks explicit usage boundaries.

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