Skip to main content
Glama

mcp_opendaw_create_stab

Create rhythmic chord stabs on a grid pattern for house, disco, and funk genres. Generate short chord hits with controlled velocity, duration, and chord voicings.

Instructions

Create rhythmic stabs — short chord jabs that define house, disco, funk.

Generates short chord hits on a rhythmic grid. Each 'x' in the rhythm pattern triggers a stab (a short chord with fast decay). Perfect for:

  • House/disco off-beat stabs

  • Funk syncopated chord punches

  • Garage/shuffle stabs

  • Filling gaps between melody notes

chords: JSON array of chord specs, cycled through. Each chord is [root_name, chord_type]. Root names: C, C#, D, D#, E, F, F#, G, G#, A, A#, B (or flats) Chord types: maj, min, dom7, maj7, min7, sus2, sus4, add9, dim, aug Example: '[["C","min7"],["F","min7"]]' cycles between Cm7 and Fm7. Single chord: '[["F","dom7"]]' — same stab repeated. rhythm: Grid pattern using 'x' (stab), '-' (rest), '.' (ghost/light stab). 16th-note grid for one bar (16 chars) or 8th-note grid (8 chars). Examples: "x-x-x-x-" (off-beat 8th stabs), "x---x---" (backbeat), "..x-..x-" (ghost stabs), "xxxx-xxx" (funky busy pattern) unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the pattern starts. octave: Octave for chord voicing (3-6, default 4 = C4 root). velocity: Base velocity for stabs (0-1, ghost stabs use 0.5x). length_beats: Total length of the stab pattern in beats (default 4 = one bar). stab_duration: Duration of each stab in beats (0.0625-1.0, default 0.5 = eighth note).

Returns notes created, chord voicings, and rhythm hits.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
chordsYes
octaveNo
rhythmNox-x-
velocityNo
start_beatNo
unit_indexNo
track_indexNo
length_beatsNo
stab_durationNo

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. It explains rhythmic grid, ghost stabs, chord cycling, and return values (notes, voicings, hits). No disclosure of destructiveness but behavior is well covered.

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?

Description is front-loaded with purpose and organized with parameter explanations. It is slightly verbose but every sentence adds value. Could be tightened without losing clarity.

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 9 parameters and output schema exists, description covers all parameters, usage examples, return values, and genres. It fully compensates for missing schema descriptions and provides complete context.

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?

Schema coverage is 0%, so description provides all meaning. It explains each parameter: chords format (JSON array), rhythm pattern (x, -, .), defaults, and examples. This adds significant value beyond 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 rhythmic stabs (short chord jabs) and specifies genres like house, disco, funk. It distinguishes from siblings by focusing on stab patterns, not arpeggios or basslines.

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 lists perfect use cases (off-beat stabs, syncopated punches, etc.) but does not explicitly mention when not to use or compare to alternatives. This is clear context but lacks exclusions.

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