Skip to main content
Glama

mcp_opendaw_create_clave

Create an Afro-Cuban clave pattern—the 5-note rhythmic skeleton that defines the feel. Choose from son, rumba, bossa nova, or 6/8 claves with 3-2 or 2-3 direction.

Instructions

Create an Afro-Cuban clave pattern — the 5-note rhythmic skeleton that defines the feel.

The clave is not a drum pattern — it's a timeline pattern that all other rhythms align to. Every Afro-Cuban rhythm has a clave direction (3-2 or 2-3) that determines where the downbeats fall relative to the clave strokes.

clave_type: "son_3_2" — Son clave, 3-side first (forward clave). Beats: 0, 0.5, 1, 2.5, 3 "son_2_3" — Son clave, 2-side first (reverse clave). Beats: 0, 1.5, 3, 3.5, 4 "rumba_3_2" — Rumba clave, 3-side first. Last stroke shifted to 3.5 (and 2.5→2.66) "rumba_2_3" — Rumba clave, 2-side first. "bossa_nova" — Bossa nova clave. Beats: 0, 2.5, 3, 4.5, 5 (over 2 bars) "6_8" — 6/8 Afro-Cuban clave. 5 strokes across 2 bars of 6/8.

bars: Pattern length in bars (2 for son/rumba, 2 for bossa, 2 for 6/8). pitch: MIDI pitch for clave strokes (76 = high wood block). velocity: Velocity 0-1. duration: Note duration in beats.

Returns notes created, clave type, and direction (3-2 or 2-3).

Example: create_clave(clave_type="son_3_2", track_index=0) create_clave(clave_type="bossa_nova", track_index=1)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
pitchNo
durationNo
velocityNo
clave_typeNoson_3_2
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 is the sole source for behavioral insight. It details that notes are created, returns notes with type and direction, but does not specify if existing notes 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 well-structured, front-loading the purpose, then providing conceptual context, parameter details, return info, and an example. It is somewhat verbose but efficient for the complexity.

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?

The description covers the tool's purpose, parameters, return values, and includes examples. It explains clave direction and types thoroughly. Missing edge cases like invalid track_index, but adequate for typical use.

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?

With 0% schema description coverage, the description adds substantial value by explaining each parameter, especially clave_type with beat positions. It compensates fully for the schema's lack of descriptions.

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 clave pattern, distinguishes it from drum patterns, and explains its role as a timeline skeleton. This sets it apart from sibling tools like create_drum_pattern.

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 explains when to use the tool (to create clave patterns) and implicitly contrasts with drum patterns. No explicit alternatives are listed, but the unique purpose is well-defined.

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