Skip to main content
Glama

mcp_opendaw_create_cadenza

Generate expressive cadenzas with rubato and irregular rhythms for musical compositions. Supports classical, romantic, jazz, and modern styles.

Instructions

Create a cadenza — an unmeasured virtuosic solo passage with rubato.

A cadenza is a solo passage where the performer has rhythmic freedom. Unlike all other tools that use quantized beat grids, cadenzas use irregular, speech-like rhythm — accelerando, rallentando, fermatas, and dramatic pauses. The notes follow a virtuosic contour: rapid runs, wide leaps, trills, and dramatic peaks.

Styles: classical — Mozart/Beethoven style: balanced phrases, cadential trills romantic — Liszt/Chopin style: dramatic octaves, cascading runs jazz — Coltrane/Parker style: bebop lines, chromatic turns modern — Ligeti/Berio style: extreme registers, clusters

The cadenza is built from segments, each with its own tempo character:

  • Flourish: rapid ascending/descending run

  • Leap: dramatic wide interval jump

  • Trill: alternating two pitches rapidly

  • Fermata: held note with pause after

  • Cascade: descending arpeggio pattern

  • Climb: gradual ascending with crescendo

Args: root: Root note name (C, C#, D, ...). scale: Scale name (major, minor, harmonic_minor, etc.). duration_beats: Approximate total duration in beats (4-64). octave: Starting MIDI octave (2-6). style: Cadenza style (classical, romantic, jazz, modern). virtuosic: If True, more rapid passages and wider leaps. breath_marks: Comma-separated beat positions for pauses/breaths. velocity: Base velocity 0-1 (cadenzas have wide dynamic range). unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, segment breakdown, and cadenza statistics.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
scaleNominor
styleNoclassical
octaveNo
velocityNo
virtuosicNo
start_beatNo
unit_indexNo
track_indexNo
breath_marksNo
duration_beatsNo

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 discloses that cadenzas use irregular, speech-like rhythm, can include accelerando, rallentando, fermatas, and pauses, and mentions output (notes created, segment breakdown, statistics). It lacks detail on potential side effects or permissions but is thorough for a creative tool.

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 sections for definition, contrast, styles, segment types, and arguments. However, it is slightly verbose; some sentences could be trimmed 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 11 parameters, no annotations, and only a mention of output schema, the description is exceptionally complete. It explains the tool's unique role, styles, segment types, all parameters, and expected return data, making it fully actionable for an AI agent.

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 description coverage is 0%, so the description must compensate. It explains every parameter (root, scale, style, octave, velocity, virtuosic, breath_marks, duration_beats, unit_index, track_index, start_beat) and adds context about segment types (Flourish, Leap, Trill, etc.), providing meaning far beyond the schema's defaults.

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 'Create a cadenza — an unmeasured virtuosic solo passage with rubato.' It defines a cadenza, contrasts it with quantized beat grid tools, and lists styles and segment types, making the purpose specific and distinguishable from many sibling tools.

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 this tool (for unmeasured, rubato passages) by contrasting with other tools that use quantized beat grids. It provides clear context but does not explicitly list alternatives or when not to use it, which would make it a 5.

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