Skip to main content
Glama

mcp_opendaw_create_comparsa

Generates Cuban comparsa percussion patterns—conga, clave, cowbell, guiro—for carnival procession styles like habanera, santiago, matanzas, conga line, or modern comparsa.

Instructions

Create Cuban comparsa — carnival procession percussion.

Comparsa is the percussion ensemble that accompanies Cuban carnival street processions (conga line). Rooted in Afro-Cuban tradition, it is the ancestor of salsa and modern Latin pop. The driving energy comes from layered conga drums with interlocking patterns.

Instruments (GM percussion mapping):

  • Conga low (54) — tumbadora, bass tone

  • Conga high (63) — quinto, slap tone

  • Conga open (64) — conga open tone

  • Clave (75) — wooden claves, the timeline

  • Cowbell (56) — cencerro, driving pulse

  • Maracas (70) — shaker

  • Guiro (73) — scraped gourd

Styles:

  • habanera: Classic Havana carnival. Conga pattern with clave 3-2, cowbell steady 8ths, maracas on offbeats. The street procession feel. 90-110 BPM.

  • santiago: Eastern Cuba, rumba-influenced. More syncopated conga patterns, guiro scrapes, claves 2-3. Looser feel.

  • matanzas: Rumba columbia roots. Quinto improvisation feel, open conga tones, sparse cowbell. Afro-Cuban spiritual energy.

  • conga_line: Street procession — marching feel. Steady bass conga on every beat, quinto syncopation, cowbell accent pattern. Designed for dancing in a line.

  • comparsa_moderna: Modern carnival — faster, denser, 16th-note maracas, driving cowbell, layered congas. Salsa-influenced energy.

Creates notes on track_index using GM percussion.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
styleNohabanera
velocityNo
tempo_bpmNo
start_beatNo
unit_indexNo
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 are provided, so the description must carry the burden. It explains that notes are created on a track using GM percussion, and lists styles and instruments. However, it does not specify whether existing notes are overwritten or appended, nor any potential 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.

Conciseness3/5

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

The purpose is front-loaded in the first sentence, but the description is lengthy with cultural background, instrument mapping, and style details. While informative, some content could be trimmed for conciseness without losing essential guidance.

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 tool's complexity (7 parameters, no annotations, has output schema), the description lacks essential parameter explanations and does not mention the output schema. It provides cultural context but omits practical invocation details.

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

Parameters1/5

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

Schema description coverage is 0%, and the description provides no explanation of the 7 parameters (bars, style, velocity, etc.). The style list in the description is not explicitly linked to the 'style' parameter. The agent gets no help understanding parameter values.

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 Cuban comparsa percussion pattern, explaining the cultural context and differentiating it from siblings like create_clave or create_songo_pattern. The verb 'create' and resource 'comparsa' are specific.

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?

Usage is implicitly clear from the domain-specific purpose, but there is no explicit guidance on when to use this tool versus alternatives like create_clave or create_tumbao. No when-not conditions are stated.

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