Skip to main content
Glama

mcp_opendaw_create_ternary_form

Compose an ABA ternary form with a contrasting B section. Choose contrast type (trio, dominant, relative, etc.), set key and bar counts, and optionally ornament the A return.

Instructions

Create ternary form — ABA with contrasting middle section.

Ternary form (ABA) is one of the most fundamental structures in Western music. The outer A sections are related (often identical, or A' with ornamentation), while the middle B section provides contrast. Used in:

  • Minuet & Trio (Haydn, Mozart): A=minuet, B=trio, A=minuet da capo

  • Da capo aria (Baroque opera): A=main aria, B=contrasting middle emotion, A=ornamented return

  • Chopin Nocturnes: A=lyrical theme, B=agitated middle, A=ornamented

  • Pop/jazz ballads: A=head, B=bridge/solo, A=head out

B section contrast types:

  • trio: Subdominant key (IV), smoother rhythm, thinner texture. Classical minuet & trio.

  • dominant: Dominant key (V), more active rhythm, builds tension. Beethoven scherzo style.

  • relative: Relative minor/major, darker/lighter character. Schubert impromptu middle sections.

  • episode: Same key, completely different melodic material. Chopin nocturne B sections.

  • development: Fragmentation of A material, modulating. Late classical/romantic expansion.

A' (return): If a_prime_ornamented=True, adds passing tones, trill-like ornaments, and slight rhythmic variation to the A material. Da capo aria / Chopin nocturne practice.

Melody on track_index, bass on track_index+1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
a_barsNo
b_barsNo
key_rootNoC
velocityNo
b_contrastNotrio
scale_nameNomajor
start_beatNo
unit_indexNo
track_indexNo
a_prime_ornamentedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries the transparency burden. It discloses key behaviors: melody is placed on track_index and bass on track_index+1, a_prime_ornamented adds ornaments to the return, and each b_contrast type has distinct musical characteristics. It does not mention side effects like overwriting existing notes, but provides substantial behavioral clarity.

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 lengthy but well-structured, with clear sections for form definition, usage examples, B section types, A' behavior, and track placement. It front-loads the primary purpose, and each section earns its place. Slightly verbose but appropriate for the musical complexity.

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

Completeness4/5

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

Given the tool's complexity (10 params, no schema descriptions, no annotations), the description covers most essential aspects: the form's structure, historical/usage contexts, parameter semantics for key musical choices, and output placement. An output schema exists, so return values are not required in the description. It is nearly complete but could mention prerequisites or unit behavior.

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

Parameters3/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 adds deep meaning for b_contrast (five types with detailed musical descriptions), a_prime_ornamented (ornamentation effect), and track_index (placement). However, parameters like a_bars, b_bars, velocity, scale_name, start_beat, and unit_index are not explained beyond their names, leaving gaps.

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 opens with 'Create ternary form — ABA with contrasting middle section,' clearly stating the verb (create), resource (ternary form), and structure (ABA). It distinguishes this tool from siblings like create_binary_form and create_sonata_form by specifying the ABA layout.

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 rich usage context, listing musical genres where ternary form is appropriate (minuet & trio, da capo aria, Chopin nocturnes, pop/jazz ballads). It explains B section contrast types and A' ornamentation, helping users decide when to use this tool. However, it does not explicitly contrast with alternative form-generation 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-ai/opendaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server