Skip to main content
Glama

mcp_opendaw_create_flamenco_compas

Generate a Flamenco compás rhythmic cycle with palmas, cajón, and golpe layers on a MIDI track, using palo, cycle count, and accent positions as input.

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
Behavior4/5

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

With no annotations, the description carries the full burden. It thoroughly explains the three rhythmic layers (palmas secas, palmas sordas, cajón/golpe), the palo-specific accent patterns, and the return payload ('notes created, instrument breakdown, accent positions, and palo info'). However, it does not disclose operational details such as whether the tool appends to existing notes, requires an existing note track, or has any side effects beyond creating notes.

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

Conciseness5/5

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

The description is long but meticulously structured: purpose, conceptual background, layered instrument roles, palo encyclopedia, and an annotated parameter list. The opening sentence front-loads the purpose, and every subsequent section adds decision-relevant information. There is no redundancy or filler.

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?

For a tool with 10 parameters, zero annotations, and a specialized cultural domain, the description is impressively complete: it explains the musical theory, enumerates palos with accents and moods, maps each pitch parameter to an instrument, and previews the return value. The only gap is operational prerequisites (e.g., whether track_index must point to an existing note track) and explicit guarantees about non-destructive behavior.

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

Parameters5/5

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

The input schema has 0% description coverage, but the description compensates completely: it explains each parameter's musical role, provides ranges (cycles 1-16, velocity 0-1), and translates MIDI pitch numbers into instrument names and notes (39 = D#1). The palo descriptions give meaningful guidance for selecting a palo based on tempo, mood, and accent structure.

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 opens with 'Create a Flamenco compás' — a specific verb and resource. It further defines compás as the cyclical rhythmic foundation of Flamenco, making the tool's function unmistakable. It clearly distinguishes itself from sibling pattern-generation tools like create_clave or create_tala by focusing on Flamenco-specific palos.

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 gives clear context on when to use this tool by contrasting Flamenco compás with Western meter and by explaining the distinct rhythmic feels of six palos. This helps the agent choose the right palo for the desired musical mood. However, it does not explicitly mention when not to use this tool or name alternative tools for non-Flamenco rhythms.

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-ai/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server