Skip to main content
Glama

mcp_opendaw_create_tumbao

Create Afro-Cuban tumbao (conga) patterns for salsa, rumba, or bolero, with control over strokes and timing to build the rhythmic foundation of salsa.

Instructions

Create an Afro-Cuban tumbao (conga) pattern — the rhythmic foundation of salsa.

The tumbao is played on congas and interacts with the clave to create the Afro-Cuban groove. The pattern features open tones (resonant, sustained), closed tones (muffled, short), and slaps (sharp, percussive). The open tone on the "and of 4" is the signature — it anticipates the downbeat.

tumbao_type: "salsa" — Standard salsa tumbao. 2-bar pattern: Bar 1: tone on &2, open on &4 Bar 2: tone on &2, open on 4 (downbeat) "salsa_slap" — Salsa with slap on beat 2 of bar 2 "rumba" — Rumba tumbao (guaguancó). Simpler, more open tones. "bolero" — Bolero tumbao. Slower feel, fewer strokes.

bars: Pattern length (2 = one tumbao cycle, repeat for longer). low_pitch: MIDI pitch for closed tones (low conga). open_pitch: MIDI pitch for open tones (mid conga). slap_pitch: MIDI pitch for slaps (high conga). velocity: Base velocity 0-1. Open tones +0.1, slaps +0.15.

Returns notes created, tumbao type, and stroke breakdown.

Example: create_tumbao(tumbao_type="salsa", track_index=0) create_tumbao(tumbao_type="salsa_slap", track_index=1, bars=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
velocityNo
low_pitchNo
open_pitchNo
slap_pitchNo
start_beatNo
unit_indexNo
track_indexNo
tumbao_typeNosalsa

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations exist, so the description fully carries the burden. It discloses that the tool creates notes, uses MIDI pitches, and returns a breakdown of notes, type, and strokes. It explains the pattern's structure (open tones, slaps, etc.) and how parameters affect sound. However, it does not mention whether existing notes on the target track are cleared or if there are side effects.

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

Conciseness4/5

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

The description is front-loaded with the core purpose and includes structured parameter explanations and examples. It is somewhat verbose in explaining the musical pattern, but this adds contextual value. Overall, it is well-organized and each section earns its place.

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 (9 parameters, no required params, no enums) and absence of annotations, the description provides substantial context about the tool's behavior and output. However, the missing parameter explanations for track_index and unit_index leave gaps. The output schema is mentioned but not detailed, though the description states return values.

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 description coverage is 0%, so the description must explain parameters. It covers tumbao_type, bars, low_pitch, open_pitch, slap_pitch, and velocity with contextual meaning. However, it omits explanations for track_index, unit_index, and start_beat, which are critical for placement. This is a significant gap.

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 Afro-Cuban tumbao (conga) pattern, a specific rhythmic foundation. It distinguishes from siblings by focusing on a particular conga pattern with subtypes like salsa, rumba, etc. The verb 'create' and resource 'tumbao' are precise.

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 explains the tumbao types and their musical contexts (salsa, rumba, bolero) but does not explicitly state when to use this tool versus alternatives like create_clave or create_cascara. Usage is implied through musical terminology, but no direct comparison or when-not-to-use guidance is provided.

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