Skip to main content
Glama

mcp_opendaw_create_turn

Create a four-note baroque turn ornament (gruppetto) around a main note, choosing upper or lower direction and interval. Adds circular motion to sustained notes in MIDI compositions.

Instructions

Create a turn — circular ornament: main → neighbor → main → other neighbor → main.

The turn (gruppetto) is one of the four essential baroque ornaments (trill, mordent, turn, appoggiatura). It circles around the main note in a four-note flourish. An upper turn goes up first (main → upper → main → lower → main), a lower turn goes down first (main → lower → main → upper → main).

Think Mozart piano concertos, Beethoven sonatas, Bach partitas. The turn adds elegance and circular motion to a sustained note.

main_pitch: The primary MIDI note (default 60 = C4). direction: "upper" (main→up→main→down→main) or "lower" (main→down→main→up→main). interval: Semitones to neighbors (default 2 = whole step). 1 = half step (diatonic). duration_beats: Total length in beats (0.5-4, default 1.0 = quarter note). velocity: Base velocity 0-1 (default 0.85). 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 turn begins.

Returns notes created, pitches used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
intervalNo
velocityNo
directionNoupper
main_pitchNo
start_beatNo
unit_indexNo
track_indexNo
duration_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations are provided, so the description carries full burden. However, it only describes the musical concept and parameter effects, omitting behavioral traits such as whether it overwrites existing notes, requires any specific state, or has side effects. The return is mentioned but not detailed. This is insufficient for an agent to understand the tool's operational impact.

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 organized with an introductory definition, musical examples, and a clear parameter list. Each sentence adds value, though the musical examples ('Think Mozart piano concertos...') are slightly verbose. Overall, it is front-loaded with the core concept and well-structured, but could be trimmed without losing essence.

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 that schema descriptions are 0% and an output schema exists (so return details are covered), the description adequately explains the turn ornament and all parameters. However, it does not address error conditions or invalid inputs (e.g., invalid unit_index) which limits completeness for an agent making robust calls. Still, it covers the core creation context well.

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?

The schema has 0% description coverage, yet the description explains every parameter in detail: main_pitch (default 60=C4), direction (upper/lower), interval (semitones, default 2), duration_beats (range and default), velocity (0-1 default), unit_index, track_index, start_beat. This adds significant meaning beyond the plain schema properties, fully compensating for the lack of schema descriptions.

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 defines 'turn' as a musical ornament with a specific pattern (main→neighbor→main→other neighbor→main) and distinguishes between upper and lower turns. It uses specific verbs ('create a turn') and explicitly names the resource (turn). Even without explicit sibling differentiation, the detailed explanation makes the purpose unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description does not provide guidance on when to use this tool versus alternatives like create_mordent or create_trill. It explains what a turn is but offers no exclusions or criteria for selection. This lack of usage context makes it harder for an agent to decide between similar ornament 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-team/opendaw-mcp'

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