Skip to main content
Glama

mcp_opendaw_create_binary_form

Creates a binary form (A|B) with two contrasting sections, optional repeats, and modulation types for Baroque or folk-style music in openDAW.

Instructions

Create binary form — two contrasting sections (A|B) with optional repeats.

Binary form is the simplest structural form in Western music: two self-contained sections, each typically repeated. The A section establishes the tonic, the B section departs and returns. Found in Baroque dance suites (Bach, Handel), folk tunes, early jazz, and many pop structures.

Modulation types (how B section relates to A):

  • dominant: B section in the dominant key (V). Classical approach — Bach two-part inventions, Baroque dance movements.

  • relative: B section in the relative minor/major. Romantic and folk approach — gentler contrast.

  • subdominant: B section in the subdominant (IV). Church hymns, modal folk tunes.

  • parallel: B section stays in same key but uses contrasting melodic material. Minimalist/folk approach.

  • no_modulation: B section identical key, same harmonic center.

With repeat=True, each section is played twice (AABB structure), matching the traditional binary form with repeat marks.

A section: stepwise melody around tonic, I-V-I harmony. B section: contrasting melody in modulated key, wider intervals, returns to tonic at end.

Creates melody on track_index, bass on track_index+1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
repeatNo
key_rootNoG
velocityNo
modulationNodominant
scale_nameNomajor
start_beatNo
unit_indexNo
track_indexNo
bars_per_sectionNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Despite no annotations, the description discloses key behavioral details: it creates melody on track_index and bass on track_index+1, explains modulation types, repeat structure, and section characteristics. It does not cover error cases or prerequisites, but for a creation tool, this is fairly transparent.

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 clear sections, but it is somewhat verbose. It front-loads the core purpose and then provides background. A bit more conciseness would improve it, but it is still organized and readable.

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?

Given the output schema exists (which likely documents return values), the description covers creation aspects adequately but lacks details on prerequisites, error conditions, or how this tool interacts with others. For a 9-parameter tool with no parameter documentation, it is moderately complete.

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?

With 0% schema coverage, the description must compensate. It explains modulation types and repeat in detail, but several parameters like velocity, start_beat, unit_index, bars_per_section, key_root, and scale_name are not described. The description adds some value but not enough to fully compensate for missing schema documentation.

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 binary form (A|B sections) with optional repeats, distinguishing it from sibling tools like create_ternary_form or create_rondo. It provides a specific verb ('create') and resource ('binary form'), and explains the musical concept.

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 provides musical context (Baroque, folk, etc.) but does not explicitly state when to use this tool over alternatives. No direct comparisons to other form creation tools or exclusions are given, which limits guidance for an agent.

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