Skip to main content
Glama

mcp_opendaw_create_fugato

Generate a fugato passage with subject entries and imitation, including countersubject and episode sections, for fugue composition.

Instructions

Create a fugato — a fugal passage with subject entries and imitation.

A fugato is a fugal section (not a full fugue) that features subject entries in imitation: the subject is stated, then answered at a different pitch level, with optional countersubject and episodic material between entries. This is the building block of fugue writing — Bach, Handel, Shostakovich fugato passages.

Unlike create_voice_exchange (transforms existing notes between tracks), fugato generates the entire fugal texture from scratch:

  • Subject: the main theme (custom or auto-generated)

  • Answer: subject restated at answer_interval (real or tonal)

  • Countersubject: a counter-melody against the answer

  • Episode: connecting material between entries (sequenced motives)

Answer modes: real — exact transposition of the subject tonal — adjusted to stay within the key (5th scaled down)

Args: root: Root note name (C, C#, D, ...). scale: Scale name (major, minor, dorian, etc.). subject_notes: Custom subject as JSON array of [pitch_offset, duration_beats]. If empty, auto-generates a subject. pitch_offset is semitones from root. Example: [[0, 0.5], [2, 0.5], [5, 1.0], [4, 0.5], [2, 0.5], [0, 1.0]] bars: Total length in bars (4-16). octave: Starting MIDI octave (2-6). voices: Number of voices (2-4). answer_interval: Transposition interval for the answer in semitones. Default 7 = perfect fifth (standard fugue answer). answer_mode: Answer type (real or tonal). include_countersubject: If True, generates a countersubject. countersubject_interval: Starting interval of countersubject from answer pitch (semitones, can be negative). include_episode: If True, generates episodic material between entries. episode_bars: Length of episode sections in bars (1-4). velocity: Base velocity 0-1. unit_index: AU index. track_index: Note track index. start_beat: Starting beat position.

Returns notes created, subject preview, voice entries, and fugato structure.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
rootNoC
scaleNominor
octaveNo
voicesNo
velocityNo
start_beatNo
unit_indexNo
answer_modeNoreal
track_indexNo
episode_barsNo
subject_notesNo
answer_intervalNo
include_episodeNo
include_countersubjectNo
countersubject_intervalNo

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, so the description carries the full burden. It explains the generation process (subject, answer, countersubject, episode) and answer modes (real/tonal). It does not mention prerequisites (e.g., whether a track must exist) or side effects, but covers the core behavior well.

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, starting with a definition, then a differentiation, followed by a clear parameter list. It is somewhat lengthy but appropriate for a complex tool; each section earns its place.

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 16 parameters, no schema descriptions, and an output schema, the description covers the output (notes, preview, structure). It lacks information about error handling, prerequisites, or track setup, but overall is fairly complete for a creative tool.

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 description coverage, the description compensates thoroughly. It explains every parameter in detail, including types, defaults, an example for subject_notes, and the meaning of answer modes. This adds significant value beyond the bare schema titles.

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 that the tool creates a 'fugato' and defines it as a fugal passage with subject entries and imitation. It distinguishes itself from a sibling tool (create_voice_exchange) by noting that fugato generates entirely new texture rather than transforming existing notes.

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_voice_exchange, providing clear context on when to use this tool. However, it does not explicitly state when not to use it or list alternative tools for similar tasks.

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