Skip to main content
Glama

mcp_opendaw_create_tala

Create Indian classical tala rhythmic cycles with vibhags and tali/khali markings, generating tabla bols and MIDI notes for specified talas like teental or ektal.

Instructions

Create an Indian classical tala — cyclic rhythmic structure with vibhag sections and tali/khali markings.

A tala is a cyclic rhythmic framework in Indian classical music. Unlike Western meter (which groups beats into uniform bars), a tala divides its cycle into vibhags (sections) of unequal length, each marked by tali (clap) or khali (wave). The theka — a sequence of named tabla strokes (bols) — defines the characteristic pattern of each tala.

The cycle (avartan) repeats, with the sam (first beat) being the strongest point. Tali beats are played with emphasis; khali beats are played softly (the "empty" section). This dynamic contrast gives Indian rhythm its distinctive breathing quality.

Talas: teental — 16 beats, 4+4+4+4 vibhags. The most common tala. Tali at beats 1, 5, 13; khali at beat 9. Dha-Dhin-Dhin-Dha pattern. ektal — 12 beats, 2+2+2+2+2+2 vibhags. Used in classical vocal and sitar. Tali at 1, 5, 9, 11; khali at 3, 7. jhaptal — 10 beats, 2+3+2+3 vibhags. Asymmetric grouping. Tali at 1, 3, 8; khali at 6. rupak — 7 beats, 3+2+2 vibhags. Unusual — starts with khali (no clap on sam). Tali at 4, 6; khali at 1. dadra — 6 beats, 3+3 vibhags. Light classical, semi-classical. Tali at 1; khali at 4. kehartwa — 8 beats, 4+4 vibhags. Tali at 1; khali at 5.

Laya (tempo): vilambit — slow, 2-beat note duration (sustained strokes) madhya — medium, 1-beat note duration drut — fast, 0.5-beat note duration

Each bol maps to a MIDI pitch representing the tabla stroke character: Dha/Dhin (bayan+dayan) -> lower register (36-38) Ti/Na/Tin/Ta (dayan) -> higher register (46-52)

Args: tala_name: Tala name (teental, ektal, jhaptal, rupak, dadra, kehartwa). cycles: Number of avartan cycles (1-16). laya: Tempo (vilambit, madhya, drut). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, vibhag structure, tali/khali positions, and bols sequence.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
layaNomadhya
cyclesNo
velocityNo
tala_nameNoteental
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries full burden of behavioral disclosure. It explains the output (notes, vibhag structure, tali/khali positions, bols) and the mapping of bols to MIDI pitches. However, it does not disclose potential side effects like overwriting existing notes or whether the tool is destructive, but given it's a creation tool, the transparency is adequate.

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 fairly long but well-organized with sections for context, tala examples, laya, bol mapping, and parameters. Every sentence provides value, though the educational content could be slightly trimmed without losing clarity. It is front-loaded with the core purpose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of Indian classical tala and the tool's 7 parameters, the description is highly complete. It explains the cyclic structure, specific tala patterns, tempo options, and bol-to-MIDI mapping. The output schema exists, so the description correctly focuses on input semantics and behavioral context without needing to detail return values.

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, so the description must compensate. It provides a clear 'Args' section with detailed explanations for each parameter, including defaults, ranges, and examples. It also explains domain-specific concepts like tala names and laya types, adding significant meaning beyond the raw schema.

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 Indian classical tala, defining it as a cyclic rhythmic structure with vibhag sections and tali/khali markings. It distinguishes from Western meter and provides specific examples of talas, making the purpose unambiguous and differentiating it from sibling tools like create_polyrhythm or create_euclidean_rhythm.

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 provides extensive context on when to use this tool, including the structure of various talas, the concept of theka, and laya tempos. However, it does not explicitly state when not to use it or compare it to alternative tools, such as other rhythm creation tools, leaving some ambiguity for an AI agent deciding between tools.

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