Skip to main content
Glama

mcp_opendaw_create_irish_trad

Generate Irish trad accompaniment with bodhrán and feet stomp patterns for reels, jigs, hornpipes, and more. Supports tune types with specific meters and rhythmic frameworks.

Instructions

Create an Irish traditional music accompaniment — bodhrán + feet for session tunes.

Irish traditional music (trad) is defined by its tune types, each with a characteristic meter and feel. The bodhrán (frame drum) and feet stomp provide the rhythmic foundation in a session. Unlike most percussion patterns, Irish accompaniment is minimal — the rhythm is carried by the melody's phrasing, and the bodhrán supports rather than drives.

tune types: "reel" — 4/4, straight 8th notes. The most common tune type. Bodhrán: downbeat + offbeat pattern. 4 beats per bar. 2 bars per phrase (AA pattern). Bright, driving. "jig" — 6/8, triplet feel. Groups of 3 eighth notes. Bodhrán: accent on beat 1 and 4 (the two downbeats of 6/8). 2 bars per phrase. Lilting, rolling feel. "hornpipe" — 4/4, dotted rhythm. 8ths are swung (long-short). Bodhrán: similar to reel but with swung feel. 2 bars per phrase. Bouncy, maritime feel. "slip_jig" — 9/8, triplet feel in 3 groups of 3. Rare, ethereal. Bodhrán: accent on 1, 4, 7. 2 bars per phrase. Dancing on air, Turlough O'Carolan style. "polka" — 2/4, fast and punchy. Common in Kerry/Sliabh Luachra. Bodhrán: strong 1 and 2. Simple, driving. 2 bars per phrase. Fast dance, march-like. "slide" — 12/8, similar to jig but faster and longer groups. Bodhrán: accent on 1, 4, 7, 10. 2 bars per phrase. Sliabh Luachra region. Fast, lilting.

Args: tune_type: Tune type (reel, jig, hornpipe, slip_jig, polka, slide). bars: Number of bars (4-32, even). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position. bodhran_pitch: Bodhrán (frame drum) MIDI pitch (36 = C1). feet_pitch: Feet stomp MIDI pitch (40 = E1). hh_pitch: Hi-hat/brush MIDI pitch (42 = F#1).

Returns notes created, tune type info, meter, and pattern breakdown.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
hh_pitchNo
velocityNo
tune_typeNoreel
feet_pitchNo
start_beatNo
unit_indexNo
track_indexNo
bodhran_pitchNo

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. The description explains what the tool creates and the rhythmic patterns for each tune type, but does not disclose side effects, permission requirements, or behavior for invalid parameters.

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 a clear introduction, a detailed breakdown of tune types, and a parameter list. While lengthy, the information is relevant and front-loaded. Could be slightly more concise.

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

Completeness3/5

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

The description thoroughly covers tune types but lacks parameter-level details. The output schema is mentioned but not described in detail. Given 9 parameters and the complexity of Irish trad, more completeness would be helpful.

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

Parameters2/5

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

Schema coverage is 0%, meaning the schema provides no descriptions. The tool description ends with a list of parameter names and defaults but does not explain each parameter's meaning beyond their names. This adds minimal value over the 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 Irish traditional music accompaniment with bodhrán and feet, specifying the genre and instruments. It distinguishes itself from sibling tools like create_afrobeat_arrangement by being genre-specific.

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 detailed context on when to use the tool (for session tunes) and explains each tune type with meter and feel. However, it does not explicitly say when not to use it or compare with alternative 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