Skip to main content
Glama

mcp_opendaw_create_mordent

Add a mordent ornament to a MIDI track with configurable pitch, direction, and duration. Rapidly alternate between main and neighbor notes for classical ornamentation.

Instructions

Create a mordent — main note → neighbor → back. A classical ornament.

The mordent is one of the four essential baroque ornaments (trill, mordent, turn, appoggiatura). It's a rapid single alternation: play the main note briefly, flick to a neighbor note, then return to the main note — all within the space of one note duration. Think Bach two-part inventions, Mozart sonatas.

An upper mordent flicks UP (main → upper neighbor → main). A lower mordent flicks DOWN (main → lower neighbor → main). The neighbor note is very short — just a flicker.

main_pitch: The primary MIDI note (default 60 = C4). direction: "upper" (main→higher→main) or "lower" (main→lower→main). interval: Semitones to the neighbor note (default 2 = whole step). Upper: 1 = half step (diatonic), 2 = whole step. Lower: -1, -2 mirror. duration_beats: Total length of the mordent in beats (0.25-4, default 0.5 = one 8th). 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 mordent 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
Behavior4/5

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

No annotations are provided, so the description carries full burden. It thoroughly explains the musical behavior: rapid single alternation, flick to neighbor, return, duration within one note. It notes the return value but does not address potential side effects (e.g., overwriting existing notes) or authorization needs. Overall, it adds significant context beyond the mute annotations.

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 paragraphs and bullet-like parameter explanations, but it is longer than necessary. Some sentences (e.g., 'Think Bach two-part inventions, Mozart sonatas') add context but could be trimmed for conciseness.

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?

For a tool with 8 parameters, no annotations, and an output schema (not detailed), the description covers musical behavior and parameter semantics thoroughly. It mentions the return value. However, it lacks information about prerequisites (e.g., existence of a track) and does not leverage any output schema details. Overall, it is adequate but not exhaustive.

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?

Schema description coverage is 0%, so the description must compensate. It does so excellently, providing clear explanations for all 8 parameters: main_pitch, direction, interval, duration_beats, velocity, unit_index, track_index, start_beat. Each parameter is described with defaults and interpretation, adding meaning far beyond the schema's titles and defaults.

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 mordent, defines it as a classical ornament, and distinguishes upper from lower mordents. It differentiates from siblings like create_appoggiatura, create_trill, and create_turn by specifying the ornament type and musical behavior.

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 gives stylistic context ('Bach two-part inventions, Mozart sonatas') but does not explicitly state when to use this tool versus alternatives. It lacks guidance on when not to use it or comparisons with related ornament tools, leaving the agent to infer usage.

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