Skip to main content
Glama

mcp_opendaw_create_second_line

Generate a New Orleans second line percussion ensemble groove — street parade beat with bass, snare, hi-hat, toms, and cymbal. Supports multiple styles: traditional, brass band, Mardi Gras Indian, jazz funeral, bounce.

Instructions

Create a New Orleans second line percussion ensemble — street parade groove.

The New Orleans second line beat is one of the foundational rhythms of American music — the root of funk, R&B, and rock drumming. Born from jazz funeral parades and brass band street processions, it combines African rhythmic sensibility with European march tradition.

Instruments:

  1. BASS DRUM — Deep boom. Plays the "street beat": downbeat + syncopated "and" of 2 and 4. The backbone that drives the parade forward.

  2. SNARE DRUM — Backbeat on 2 and 4 with ghost notes on the "e" and "a" of beats. Loose, funky, slightly behind the beat feel.

  3. HI-HAT — Charleston rhythm (beat 1, "and" of 2, beat 3, "and" of 4) or straight 8ths depending on style. The pulse-keeper.

  4. TOM-TOM — Fills at phrase ends, rhythmic calls in Indian style. Adds melodic colour to the percussion arrangement.

  5. CYMBAL — Crash accents on phrase starts. Sparse, ceremonial.

styles: "traditional" — Classic street parade (early 20th century). Steady Charleston hi-hat, backbeat snare, syncopated bass. The original second line groove. "brass_band" — Modern brass band style (Dirty Dozen, Rebirth). Denser, funkier. More ghost notes, tom rolls, 8th-note hi-hat. "mardi_gras_indian" — Mardi Gras Indian style (Wild Tchoupitoulas). Call-and- response between tom and snare. Ritualistic, tribal. Sparse bass, tom-driven. "jazz_funeral" — Dirge to celebration. Bar 1: slow, sparse (dirge on the way to the cemetery). Bar 2: upbeat, driving (celebration on the way back). Dramatic dynamic shift. "bounce" — New Orleans bounce (1980s+, DJ Jimi, Magnolia Shorty). "Triggerman" double-time bass drum, 16th-note hi-hat, backbeat snare. The foundation of NOLA hip-hop.

Args: bars: Pattern length (4-16, even). style: Style name. velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. bass_pitch: Bass drum MIDI pitch (36 = C1). snare_pitch: Snare drum MIDI pitch (38 = D1). hi_hat_pitch: Hi-hat MIDI pitch (42 = F#1). tom_pitch: Tom-tom MIDI pitch (45 = A1). cymbal_pitch: Crash cymbal MIDI pitch (49 = C#2).

Returns notes created, instrument breakdown, and style info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
styleNotraditional
velocityNo
tom_pitchNo
bass_pitchNo
start_beatNo
unit_indexNo
snare_pitchNo
track_indexNo
cymbal_pitchNo
hi_hat_pitchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations provided. The description adds some context (instruments, styles, return info) but fails to disclose key behavioral traits such as side effects, required permissions, or whether existing notes are modified.

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 verbose with historical and educational content that, while informative, is not essential for an AI agent. The core purpose is front-loaded, but the lengthy instrument and style explanations could be more compact.

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 covers instruments, styles, and parameters thoroughly. With an output schema present, return values are explained. However, missing prerequisites (e.g., required track setup) and integration context reduce completeness.

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

Parameters5/5

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

Schema coverage is 0%, but the description includes an 'Args' section with meaningful descriptions for all 11 parameters (e.g., 'bars: Pattern length (4-16, even)', 'style: Style name'). This compensates fully, adding value beyond type and 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 clearly states the tool creates a 'New Orleans second line percussion ensemble' with specific instruments and styles. It distinguishes from sibling tools like mcp_opendaw_create_samba_pattern or create_boom_bap by focusing on a unique rhythmic tradition.

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

Usage Guidelines2/5

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

The description does not explicitly state when to use this tool versus alternatives. It implies usage for creating second line patterns, but lacks when-not guidance or comparisons to other creation tools in the sibling list.

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