Skip to main content
Glama

mcp_opendaw_create_cascara

Create an Afro-Cuban cáscara pattern for timbales, filling rhythmic gaps around the clave with high and low strokes. Supports son, guaguanco, and mambo types.

Instructions

Create an Afro-Cuban cáscara pattern — the timbale shell rhythm that fills space around the clave.

Cáscara ("shell") is played on the sides of the timbale drums. It weaves between the clave and tumbao, filling the rhythmic gaps with a flowing, continuous feel. Together with clave and tumbao, it forms the three pillars of the Afro-Cuban rhythm section. The pattern uses two stroke heights: high (rim/edge, accented) and low (shell body, unaccented), creating a call-and-response within the pattern.

cascara_type: "son_3_2" — Son cáscara, 3-2 direction (forward clave). Bar 1: &2 high, 3 low, &3 high, &4 low Bar 2: &2 high, 3 low, &3 high, 4 low "son_2_3" — Son cáscara, 2-3 direction (reverse clave). Bar 1: &2 high, 3 low, &3 high, 4 low Bar 2: &2 high, 3 low, &3 high, &4 low "guaguanco" — Rumba guaguancó cáscara. Adds ghost strokes on beat 1 and &1 of each bar for a denser, more driving feel. "mambo" — Mambo cáscara. Adds syncopated accents on &4 of bar 2 and a fill on beat 4 of bar 2. Brighter, more showy.

bars: Pattern length (2 = one cáscara cycle, repeat for longer). high_pitch: MIDI pitch for high strokes (rim/edge of timbale, 76 = high wood block). low_pitch: MIDI pitch for low strokes (shell body, 60 = mid tom). velocity: Base velocity 0-1. High strokes +0.1, low strokes -0.05.

Returns notes created, cáscara type, direction, and stroke breakdown.

Example: create_cascara(cascara_type="son_3_2", track_index=0) create_cascara(cascara_type="guaguanco", track_index=1, bars=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
velocityNo
low_pitchNo
high_pitchNo
start_beatNo
unit_indexNo
track_indexNo
cascara_typeNoson_3_2

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 discloses that high/low stroke pitches are used, velocity adjustments, and return values (notes created, type, direction). It does not mention destructive actions or permissions, but covers key behavioral traits.

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 purpose and musical context, then details each parameter and type, ending with examples. It is somewhat lengthy but every sentence adds value. Minor redundancy in explaining the three pillars.

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 (8 parameters, musical pattern) and absent schema descriptions, the description is comprehensive about musical intent and parameter effects. It covers return values and includes examples. Missing details on positional parameters like start_beat prevent a higher score.

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 must compensate. It explains cascara_type, bars, high_pitch, low_pitch, and velocity in detail, including stroke patterns and velocity offsets. However, start_beat, unit_index, and track_index are not described, leaving gaps.

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 an Afro-Cuban cáscara pattern. It explains what cáscara is and its role alongside clave and tumbao, distinguishing it from sibling pattern tools like create_clave and create_tumbao.

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 implies usage for cáscara patterns within Afro-Cuban rhythm sections, mentioning clave and tumbao as counterparts. However, it lacks explicit guidance on when to use this tool versus alternatives, or when not to use it.

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