Skip to main content
Glama

mcp_opendaw_create_trill

Create rapid alternating note patterns (trills) for musical ornaments across genres. Specify pitches, rate, duration, accent, and positioning.

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

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

No annotations are provided, so the description must fully disclose behavior. It describes note creation, alternation rate, accent options, and return value, but does not mention side effects (e.g., overwriting existing notes) or prerequisites (e.g., required track setup).

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

Conciseness3/5

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

The description is moderately concise with a front-loaded purpose, but the parameter list at the end duplicates schema info. Some sentences on genre context are helpful but could be condensed.

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

Completeness3/5

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

Given 10 parameters, no annotations, no schema descriptions, and an output schema present, the description covers the concept and most parameter functions. However, it lacks detailed parameter semantics and behavioral transparency, leaving gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate. It lists parameters and defaults but adds little explanation beyond the schema. For example, 'rate' values are listed without explanation of triplet interpretations, and no examples or constraints are provided.

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 trill, defines it as rapid alternation between two notes, and provides genre-specific context (classical, jazz, metal, electronic). This distinguishes it from sibling ornament tools like create_mordent or create_turn.

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 provides clear context on when to use the tool (for trills across multiple genres) but does not explicitly state when not to use it or compare with alternatives. The genre mentions help guide appropriate use.

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