Skip to main content
Glama

mcp_opendaw_create_songo_pattern

Create a songo drum pattern for modern Latin music production, with variations for classic, modern, fusion, and songo-funk styles.

Instructions

Create a songo drum pattern — the Cuban drum-kit fusion that revolutionized Latin music.

Songo emerged in the 1970s with Los Van Van (drummer Changuito). It fused son montuno, rumba, jazz, and rock drumming into a single drum-kit pattern — the first time Cuban percussion was adapted to a Western kit. Unlike clave (a timeline), tumbao (congas), or cascara (timbale shell), songo is a complete drum-kit groove: kick + snare + hi-hat + tom accents working together as one synchronized engine. It became the foundation of modern salsa, timba, and Latin jazz drumming.

The pattern is 2 bars in 4/4. Kick plays syncopated bombo notes, snare alternates between rim clicks and open hits, hi-hat plays a continuous 8th-note pattern with accents, and toms fill rhythmic gaps with tonal accents. The feel is loose but locked — every stroke relates to the 3-2 clave without explicitly playing it.

variations: "classic" — Original Los Van Van songo. Kick on 1, 2.5, 4, 6.5. Snare rim clicks on 3, 7. Open snare on 4.5. HH 8ths. "modern" — Timba-era songo (1990s+). Denser kick, ghost snare notes, tom fills on bar 2. More aggressive, busier. "fusion" — Jazz-influenced. Ride-like HH pattern, syncopated kick displacements, brush snare. Los Hermanos approach. "songo_funk" — Songo with funk inflection. Kick on 1, 1.75, 3.5, 4.75. Ghost snare 16ths. Backbeat on 2 and 4. Groove-oriented.

bars: Pattern length (2-16, must be even for 2-bar cycle). velocity: Base velocity (0-1). kick_pitch: MIDI pitch for kick drum (36 = C1). snare_pitch: MIDI pitch for snare (38 = D1). hh_pitch: MIDI pitch for hi-hat (42 = F#1). tom_pitch: MIDI pitch for tom accents (45 = A1).

Args: bars: Pattern length in bars (2-16, even). variation: Pattern variation (classic, modern, fusion, songo_funk). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. kick_pitch: Kick MIDI pitch. snare_pitch: Snare MIDI pitch. hh_pitch: Hi-hat MIDI pitch. tom_pitch: Tom MIDI pitch.

Returns notes created, stroke breakdown, and pattern info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
hh_pitchNo
velocityNo
tom_pitchNo
variationNoclassic
kick_pitchNo
start_beatNo
unit_indexNo
snare_pitchNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the pattern structure and variations, but does not disclose whether notes are added or overwritten, authentication needs, or side effects. Output is described as notes, stroke breakdown, and pattern info, but operational details like track setup are missing.

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?

Description is lengthy with a historical paragraph. While educational, it is somewhat verbose for an AI agent. However, it is well-structured with clear variation descriptions and front-loaded purpose.

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 the complexity (4 variations, 10 parameters, output schema exists), the description covers musical context, variation details, and parameter basics. It mentions output content. Gaps: unit_index, track_index, and start_beat usage not fully explained. Overall adequate.

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 has 10 parameters with defaults but no descriptions. Description adds meaning for bars, variation, velocity, and pitches (e.g., '36 = C1'). However, unit_index, track_index, and start_beat are mentioned but not fully explained. Overall adds significant value beyond the schema.

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 songo drum pattern, a specific Cuban drum-kit fusion. It distinguishes songo from other patterns like clave, cascara, and tumbao, which are sibling tools. The purpose is specific and differentiated.

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 provides context for songo (Latin music, salsa, timba, Latin jazz) but lacks explicit guidance on when to use this tool versus alternatives like clave or tumbao. It implies usage through musical context but does not state when not to use or list competing tools.

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