Skip to main content
Glama

mcp_opendaw_create_mordent

Create a mordent ornament (main note, neighbor, return) with adjustable direction, interval, duration, and velocity for authentic baroque phrasing.

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
Behavior3/5

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

There are no annotations, so the description must disclose behavior. It explains the note pattern, parameter defaults, and return value, but does not disclose potential side effects like whether notes are inserted or appended, or any prerequisites beyond specifying unit/track indices.

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-organized, front-loading the purpose, but includes several paragraphs of music theory that, while helpful, could be trimmed; still, no wasted filler and the parameter list is clear.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

All parameters are explained with defaults and ranges, the return value is stated, and the musical behavior is fully described. Given the absence of schema descriptions, the description is complete enough for an agent to invoke the tool correctly.

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%, and the description compensates thoroughly by documenting all 8 parameters with defaults, ranges, and musical meaning (e.g., interval 1=half step, 2=whole step; duration 0.25-4 beats).

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 opens with 'Create a mordent — main note → neighbor → back' which clearly states the action and output. It distinguishes this from sibling ornament tools by specifying the mordent pattern and its upper/lower variants.

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 provides musical context (baroque ornament, Bach/Mozart) implying when a mordent is appropriate, but does not explicitly contrast it with create_trill, create_turn, or create_appoggiatura, or state when not to use this tool.

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-ai/opendaw-mcp'

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