Skip to main content
Glama

mcp_opendaw_create_sonata_form

Create a sonata form composition by specifying key, scale, bar lengths for exposition, development, and recapitulation sections.

Instructions

Create sonata form — exposition, development, recapitulation.

Sonata form is the structural foundation of classical symphonies, sonatas, string quartets, and concertos from Haydn through Mahler. Three main sections:

  1. EXPOSITION (bars 1-N): Two contrasting themes.

    • Theme 1 in the home key (tonic): stepwise, lyrical, conjunct

    • Transition: modulates from tonic to dominant (or relative major if minor key)

    • Theme 2 in the new key: more rhythmic, wider intervals

    • Closing group: cadential figures in the new key

  2. DEVELOPMENT (bars N+1 to N+M): Fragmentation and modulations.

    • Takes fragments from Theme 1 and Theme 2

    • Sequences through related keys (iii, vi, ii, IV)

    • Builds tension through rising sequences

    • Retransition: dominant pedal leading back to tonic

  3. RECAPITULATION (bars N+M+1 to end): Both themes in the tonic.

    • Theme 1 returns in tonic (as in exposition)

    • NO modulation — Theme 2 now in tonic (not dominant)

    • Closing group in tonic

    • Optional coda (4 bars): final cadential reinforcement

Melody track: track_index. Bass track: track_index + 1. The development section uses sequence-based modulation, the hallmark of classical development technique.

Scale options: major, minor, dorian, phrygian, lydian, mixolydian, aeolian, locrian, harmonic_minor, melodic_minor, pentatonic_major, pentatonic_minor, blues, whole_tone.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
key_rootNoC
velocityNo
recap_barsNo
scale_nameNomajor
start_beatNo
unit_indexNo
track_indexNo
exposition_barsNo
development_barsNo

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, so the description must carry the burden. It explains the structural output and track layout (melody track, bass track) but does not explicitly state that MIDI notes will be generated on the specified tracks or disclose side effects like overwriting existing data.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with numbered sections but is verbose, including extensive musical theory that may not be necessary for tool selection. It is front-loaded with the purpose, but the length reduces conciseness.

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

Completeness2/5

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

Given the tool's complexity (9 parameters, no schema descriptions, no annotations), the description fails to cover key aspects like parameter defaults and behavior for parameters like start_beat, unit_index, and velocity. The output schema is missing, further reducing completeness.

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 description coverage is 0%, so the description must compensate. It lists scale_name options and implicitly explains track_index and track_index+1 for bass, but does not describe other parameters like key_root, velocity, exposition_bars, etc. Only partial parameter meaning is provided.

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 a sonata form structure with three sections (exposition, development, recapitulation). It uses specific verbs and resources, distinguishing it from other 'create_*' tools by providing detailed classical music form content.

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 explains the musical context of sonata form but does not explicitly state when to use this tool vs. other form tools (e.g., create_binary_form, create_ternary_form). Usage is implied but not compared or contrasted with alternatives.

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