Skip to main content
Glama

mcp_opendaw_create_flamenco_compas

Generate a Flamenco compás rhythm cycle with palmas, cajón, and golpe for a chosen palo (e.g., bulerías, soleá) and number of cycles.

Instructions

Create a Flamenco compás — the cyclical rhythmic foundation of Flamenco.

Flamenco compás is the rhythmic cycle that defines each palo (form). Unlike Western meter (uniform bars), Flamenco uses a 12-beat cycle with accents on specific beats (typically 3, 6, 8, 10, 12). The accents create the characteristic Flamenco feel — a tension between the expected downbeat and where the accents actually fall.

The compás is marked by three layers:

  1. PALMAS SECAS — Sharp, dry handclaps on accented beats. The "skeleton" of the compás. Loud, precise.

  2. PALMAS SORDAS — Muffled handclaps on unaccented beats. The "flesh" — fills the gaps between secas. Softer, cupped hands.

  3. CAJÓN — Peruvian box drum adapted to Flamenco. Plays the bass pulse, usually on beats 1 and the main accents. Resonant, deep.

  4. GOLPE — Table tap / footwork accent. Sharp percussive hits for dramatic moments, often at the end of a compás cycle.

palos (forms): "bulerias" — 12 beats, accents on 12, 3, 6, 8, 10. Fast, festive. The most modern and popular palo. Starts on 12. "solea" — 12 beats, accents on 3, 6, 8, 10, 12. Slow, solemn. The "mother of Flamenco". Deep, expressive. "alegrias" — 12 beats, accents on 3, 6, 12 (lighter), 8, 10. Joyful. From Cádiz. Mid-fast tempo. "siguiriyas" — 12 beats, accents on 3, 6, 8, 11 (asymmetric grouping 3+2+3+2+2). Slow, tragic. The most jondo (deep) palo. "tangos" — 4 beats, accents on 1, 3. Simple 4/4 feel, the most accessible palo. Rhythmic, earthy. "rumba" — 4 beats, accents on 1, 2.5, 3 (syncopated). The most accessible Flamenco-pop form. Gypsy Kings style.

Args: palo: Flamenco form (bulerias, solea, alegrias, seguiriyas, tangos, rumba). cycles: Number of compás cycles (1-16). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. palmas_secas_pitch: Palmas secas (sharp clap) MIDI pitch (39 = D#1). palmas_sordas_pitch: Palmas sordas (muffled clap) MIDI pitch (42 = F#1). cajon_pitch: Cajón (box drum) MIDI pitch (36 = C1). golpe_pitch: Golpe (tap) MIDI pitch (50 = D2).

Returns notes created, instrument breakdown, accent positions, and palo info.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
paloNobulerias
cyclesNo
velocityNo
start_beatNo
unit_indexNo
cajon_pitchNo
golpe_pitchNo
track_indexNo
palmas_secas_pitchNo
palmas_sordas_pitchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description must fully convey behavioral traits. It explains the creation of four layers but omits whether it overwrites existing notes, requires specific track types, or has side effects. Details like 'returns notes created' hint at behavior but are insufficient for a mutation tool with zero annotation coverage.

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 well-structured with headers and bullet points, but the educational introduction about Flamenco, while valuable, adds length. Each section serves a purpose, but some redundancy could be trimmed without losing clarity.

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 10 parameters, no annotations, and an output schema, the description is fairly complete—explains the rhythmic concept, lists parameters, and mentions return values. However, it lacks guidance on how the compás integrates with existing tracks (track_index, unit_index) and the impact on existing notes, leaving some context gaps.

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 coverage is 0%, so the description compensates by listing all parameters with brief descriptions, defaults, and some musical context (e.g., pitch names). However, unit_index and track_index lack clear explanation of their roles, and the description could better clarify parameter interactions.

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 Flamenco compás, the rhythmic foundation, and distinguishes it from Western meter. It lists palos with beat patterns, making the purpose highly specific and differentiated from sibling creation tools.

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 rich context about Flamenco but does not explicitly state when to use this tool vs alternatives (e.g., create_clave, create_samba_pattern). No 'when not to use' guidance, leaving the agent to infer usage from the specialized content.

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