Skip to main content
Glama

mcp_opendaw_create_trill

Generate a musical trill by rapidly alternating between two notes. Specify pitches, rate, duration, accent, and starting note to create the ornament in your DAW project.

Instructions

Create a trill — rapid alternation between two notes.

A fundamental ornament used across classical (baroque trills, mordents), jazz (shake), metal (tremolo picking), and electronic (LFO-like patterns). Two notes alternate at the specified rate for the given duration. Upper note can be accented (baroque style) or both equally loud.

lower_pitch: Lower MIDI note of the trill (default 60 = C4). upper_pitch: Upper MIDI note, typically 1-2 semitones above (default 62 = D4). rate: Trill speed — "32nd", "16th", "8th", "32t" (triplet 32nd), "16t" (triplet 16th). duration_beats: Total length of the trill in beats (0.5-32, default 4 = 1 bar at 4/4). accent_upper: If true, upper note is louder (baroque style). If false, equal velocity. start_with_upper: If true, trill starts on upper note (some baroque conventions). 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 trill begins.

Returns notes created, rate, note count.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rateNo16th
velocityNo
start_beatNo
unit_indexNo
lower_pitchNo
track_indexNo
upper_pitchNo
accent_upperNo
duration_beatsNo
start_with_upperNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden and does well: it explains alternation behavior, accent/start options, target track selection, and return value ('Returns notes created, rate, note count'). It does not disclose all edge-case side effects (e.g., overwrites, failures), but enough is provided for safe invocation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with a one-line definition, then uses a compact parameter listing. The genre context is relevant and not bloated; every section adds value.

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?

The tool has 10 optional parameters and no annotations, but the description covers every parameter, provides target selection semantics, and states the output summary. This is complete enough for an agent to invoke 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%, but the free-text description enumerates and explains all 10 parameters with defaults, ranges, and semantics (e.g., rate values '32nd','16t', duration 0.5-32). This fully compensates for the schema's lack of param 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 opens with 'Create a trill — rapid alternation between two notes,' providing a specific verb and resource. It clearly distinguishes this from ornament-generation siblings like create_mordent or create_turn by defining the trill concept and its musical contexts.

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?

It gives clear context for when a trill is appropriate (baroque, jazz, metal, electronic) and explains the mechanism. However, it never names alternative sibling tools or states when NOT to use it, so exclusions are missing.

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