Skip to main content
Glama

mcp_opendaw_create_samba_pattern

Creates multi-instrument samba percussion patterns with layers for surdo, caixa, tamborim, chocalho, and repique, supporting batucada, samba_enredo, pagode, and samba_funk styles.

Instructions

Create a Brazilian samba percussion ensemble pattern — multi-instrument layered groove.

Samba is the heartbeat of Brazilian music — a multi-instrument percussion ensemble where each drum has its own pattern, and the layers interlock to create a dense, driving groove. Unlike songo (a single drum-kit pattern), samba is an ensemble: each instrument plays independently, and the combination creates the full sound. Batucada (the carnival samba style) can have 300+ percussionists, each on one drum.

The 5 core instruments:

  1. SURDO — The bass drum. Plays on beats 1 and 3 (the "floor"). Low, resonant, the heartbeat. Surdo marcado (marked) = steady, surdo virado (turned) = syncopated.

  2. CAIXA — The snare drum. Plays continuous 16th notes with a backbeat accent on beats 2 and 4. The "glue" of the ensemble, filling the middle register.

  3. TAMBORIM — Small handheld drum. Plays a syncopated 16th pattern with rim taps, the "conversation" layer. Often uses "virada" (turn) fills.

  4. CHOCALHO — Shaker. Plays continuous 16th notes, the "wash" that keeps the time steady. Always present, rarely varied.

  5. REPIQUE — Lead drum. Plays calls, fills, and syncopated accents that cue the ensemble. The "conductor" of the bateria.

styles: "batucada" — Carnival samba (Rio de Janeiro). Dense, fast, all 5 instruments. Surdo on 1+3, caixa 16ths, tamborim syncopated, chocalho 16ths, repique accents. "samba_enredo" — Samba school parade style. More structured, surdo patterns more varied, repique has call-and-response. "pagode" — Backyard samba (informal). Lighter, no repique, tamborim simpler. More swing, less density. "samba_funk" — Samba-funk fusion. Surdo pattern funkier, caixa with ghost notes, tamborim 16ths, chocalho offbeats.

bars: Pattern length (2-16, even for 2-bar cycle). velocity: Base velocity (0-1). surdo_pitch: Surdo (bass drum) MIDI pitch (36 = C1). caixa_pitch: Caixa (snare) MIDI pitch (38 = D1). tamborim_pitch: Tamborim MIDI pitch (42 = F#1). chocalho_pitch: Chocalho (shaker) MIDI pitch (46 = A#1). repique_pitch: Repique (lead drum) MIDI pitch (50 = D2).

Args: bars: Pattern length in bars (2-16, even). style: Samba style (batucada, samba_enredo, pagode, samba_funk). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. surdo_pitch: Surdo MIDI pitch. caixa_pitch: Caixa MIDI pitch. tamborim_pitch: Tamborim MIDI pitch. chocalho_pitch: Chocalho MIDI pitch. repique_pitch: Repique MIDI pitch.

Returns notes created, instrument breakdown, and pattern info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
styleNobatucada
velocityNo
start_beatNo
unit_indexNo
caixa_pitchNo
surdo_pitchNo
track_indexNo
repique_pitchNo
chocalho_pitchNo
tamborim_pitchNo

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 carries full burden. It explains that the tool creates a multi-instrument pattern, describing each instrument's role and output. It states it returns notes and instrument breakdown. It does not disclose whether it overwrites existing notes or appends, but the creation aspect is clear. The description provides good insight into the tool's behavior without contradiction.

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

Conciseness2/5

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

The description is overly verbose, devoting large paragraphs to educational content about samba instruments and styles. While informative, this is not structured for efficient agent use. The 'Args' list is redundant with the input schema and adds no new information. Front-loading is present but the bulk of the text could be trimmed significantly.

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

Completeness2/5

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

Given the complexity (11 parameters, multi-instrument output), the description lacks explanations for critical positional parameters (unit_index, track_index, start_beat). It vaguely describes output as 'notes created, instrument breakdown, and pattern info' without details. The educational content is thorough but does not cover operational aspects needed for correct invocation. The output schema exists but is not referenced to clarify return structure.

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

Parameters2/5

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

Schema coverage is 0%, so description must compensate. It adds meaning for instrument pitches (e.g., surdo_pitch: 'Surdo (bass drum) MIDI pitch (36 = C1)') and style/bars/velocity. However, it fails to explain critical parameters like unit_index, track_index, and start_beat, which are essential for note placement. The 'Args' section merely repeats names without description. Overall, the description adds meaning for only a subset of parameters.

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 it creates a Brazilian samba percussion ensemble pattern, distinguishing it from the sibling songo pattern and explicitly contrasting it as a multi-instrument layered groove. The verb 'create' plus resource 'samba pattern' is specific and unambiguous.

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 explicitly contrasts samba with songo (single drum-kit pattern), guiding the agent to choose this tool over create_songo_pattern. It also details four distinct styles with characteristics, implying when each is appropriate. However, it does not explicitly state when not to use it or mention prerequisites like required tracks or instrument configurations.

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