Skip to main content
Glama

mcp_opendaw_create_fugue

Generate a fugue with subject, answer, and countersubject, supporting tonal or real answers, multiple voices, stretto, and configurable entry delay.

Instructions

Create a fugue — polyphonic composition with subject, answer, and countersubject.

The most complex contrapuntal form. A subject (main theme) is stated in one voice, then imitated in others with a tonal or real answer. Optional countersubject provides contrasting counterpoint. Stretto mode overlaps voice entries for climactic density. Unlike create_canon (strict imitation), a fugue uses tonal answers (adjusted intervals) and independent countersubjects.

subject: Comma-separated MIDI pitches of the fugue subject (e.g. "60,62,64,65"). voices: Number of voices (2-5, default 3). More voices = denser counterpoint. entry_delay_beats: Beats between voice entries (2-8, default 4). answer_type: "tonal" (fifth up, adjusted) or "real" (exact transposition). countersubject: Comma-separated MIDI pitches of countersubject (optional). If empty, no countersubject. Must be same length as subject. key_root: Key root for tonal answer calculation (e.g. "C", "F#", "Bb"). key_mode: "major" or "minor" — affects tonal answer adjustment. note_duration: Note duration as fraction of beat (0-1, default 0.9 = legato). velocity: Base velocity for first voice (0-1, default 0.75). velocity_decay: Velocity reduction per voice (0-0.3, default 0.1). stretto: If true, later voices enter before previous finishes subject. unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the first voice begins.

Returns notes created, voice count, subject length, answer type, stretto status.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voicesNo
strettoNo
subjectNo60,62,64,65,64,62,60,57
key_modeNomajor
key_rootNoC
velocityNo
start_beatNo
unit_indexNo
answer_typeNotonal
track_indexNo
note_durationNo
countersubjectNo
velocity_decayNo
entry_delay_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description explains musical behavior (subject, answer, stretto) and parameter effects but does not disclose operational side effects like whether it overwrites existing notes or requires a pre-existing track. No annotations are provided.

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: purpose first, then musical context, sibling comparison, and parameter details. It is efficient, though slightly lengthy due to parameter explanations, which are necessary given no schema descriptions.

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?

The description covers musical concept, parameters, return values, and alternative tool. However, it omits prerequisites (e.g., need for a note track), error conditions, and example usage. Given the complexity, completeness is good but not full.

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?

With 0% schema coverage, the description compensates fully by explaining all 14 parameters, including defaults, valid ranges (e.g., velocity: 0-1), and constraints (countersubject must match subject length). This adds essential meaning.

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 it creates a fugue, a specific polyphonic composition, and contrasts it with create_canon, distinguishing it from a sibling tool. The verb 'create' and resource 'fugue' are precise.

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 explicitly contrasts with create_canon, explaining when to use a fugue (tonal answers, countersubject) versus strict imitation. However, it does not mention other alternatives or non-use cases.

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