Skip to main content
Glama

mcp_opendaw_create_rondo

Generates a rondo musical form with a recurring theme and contrasting episodes, supporting classical, pop, jazz, and other structures. Automatically creates melody and bass parts on specified tracks.

Instructions

Create a rondo — recurring theme alternating with contrasting episodes.

A rondo is a structural form where a principal theme (A) alternates with contrasting episodes (B, C, D). The theme always returns, providing unity while episodes provide contrast and development.

Form types:

  • simple: ABA (3 sections). Miniature rondo, common in character pieces.

  • classical: ABACA (5 sections). Standard classical rondo (Mozart, Beethoven). A=tonic, B=dominant/relative, C=more distant.

  • seven_part: ABACABA (7 sections). Large rondo, Beethoven Op.51, Chopin Op.16. Extended with second return of B before final A.

  • pop_rock: ABABCB (6 sections). Pop/rock structure masquerading as rondo — verse-chorus-verse-chorus-bridge-chorus. A=verse, B=chorus, C=bridge.

  • jazz: ABAC (4 sections). Jazz standard form — theme, improvisation feel, theme, contrast. A=head, B=solo section, C=trading.

Key root: C, C#, Db, D, ... B. Scale: major, minor, dorian, phrygian, lydian, mixolydian, aeolian, locrian, harmonic_minor, melodic_minor, pentatonic_major, pentatonic_minor, blues, whole_tone.

The A theme uses tonic scale degrees (0, 2, 4, 2, 0). B episode uses dominant/relative degrees (4, 6, 2, 6, 4) — brighter. C episode uses more distant degrees (5, 1, 3, 1, 5) — contrasting. Each section is bars_per_section bars long.

Creates sections sequentially on track_index (melody on track_index, bass on track_index+1).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
key_rootNoC
velocityNo
form_typeNoclassical
tempo_bpmNo
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?

No annotations are provided, but the description discloses significant behavioral details: sections are created sequentially on specific tracks, degree patterns for each section, and the number of bars per section. It does not mention destructiveness or undo, which is acceptable for a creation 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 and front-loaded with the purpose. It provides educational content but is somewhat verbose. Every sentence adds value, though some musical theory could be condensed.

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 9 parameters, lack of output schema, and no annotations, the description provides good context for the rondo structure but fails to explain all parameters. It does not describe the return value or side effects. Adequate but with gaps.

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%. The description explains some parameters (key_root, scale_name, form_type, bars_per_section, track_index) but does not cover velocity, tempo_bpm, start_beat, or unit_index. This leaves several parameters unexplained, requiring the agent to rely on naming conventions.

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 rondo' and provides a thorough explanation of what a rondo is, including form types, scale options, and structural details. It distinguishes this from many other create_* tools by focusing on the rondo form.

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 purpose is clear and the description implies when to use this tool (when a rondo form is desired). However, it lacks explicit guidance on when not to use it or alternatives. The form type options provide some context.

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