Skip to main content
Glama

mcp_opendaw_set_articulation

Set legato, staccato, or tenuto articulation for notes on selected tracks, controlling note spacing and overlap in openDAW.

Instructions

Set articulation for notes — legato, staccato, or tenuto.

Articulation defines how notes connect to each other — the space or overlap between consecutive notes. This is what makes strings sound smooth (legato) or plucky (staccato), and it's separate from pitch and velocity.

Three articulations:

  • "legato" — each note extends to the start of the next note (minus a micro_gap in PPQN for articulation separation). Notes flow into each other seamlessly. Use for smooth string lines, vocal phrases, wind instruments, lead melodies.

  • "staccato" — each note is shortened to staccato_ratio of the distance to the next note. 0.5 = half the gap, 0.25 = very short and detached, 0.75 = portato (lightly separated). Creates space between notes.

  • "tenuto" — each note holds to its full available duration (up to the next note's start, no gap). Slightly longer than legato — full value with no separation. Use for sustained passages, horn sustains.

The last note in each region keeps its original duration (no next note to reference). Notes at the same position (chords) are treated as one unit — they all get the same treatment based on the next distinct position.

unit_index: AU index (-1 = all AUs). track_index: Note track index (-1 = all note tracks on the AU). region_index: Region index (-1 = all regions on the track). articulation: "legato", "staccato", or "tenuto". staccato_ratio: For "staccato" — fraction of gap to fill (0.1-0.9, default 0.5 = half the available time). micro_gap: For "legato" — PPQN gap to leave between notes (default 20, ~1/48 of a beat). 0 = notes touch exactly. Higher = more separation.

Returns per-track notes adjusted, articulation type.

Example:

Smooth legato strings

set_articulation(unit_index=0, track_index=2, articulation="legato")

Crisp staccato — 30% of available time

set_articulation(unit_index=0, track_index=2, articulation="staccato", staccato_ratio=0.3)

Full tenuto — horns holding full value

set_articulation(unit_index=0, track_index=3, articulation="tenuto")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
micro_gapNo
unit_indexNo
track_indexNo
articulationNolegato
region_indexNo
staccato_ratioNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

The description explains key behavioral traits: how each articulation affects note lengths, edge cases (last note, chords), and the return value. Since no annotations are provided, the description carries the full burden. It could benefit from noting irreversibility or undo availability, but overall is transparent.

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 well-organized: purpose statement, articulation explanations, parameter list, edge cases, and an example. Every sentence earns its place, and the structure is front-loaded and easy to scan. Length is justified by complexity.

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?

Given the complexity (6 parameters, 3 articulation modes, edge cases) and the existence of an output schema, the description is thorough. It covers all necessary aspects for an agent to use the tool correctly, including parameter semantics and behavioral caveats.

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?

With 0% schema description coverage, the description fully compensates by explaining each of the 6 parameters, including defaults, unit indices, and the meaning of staccato_ratio and micro_gap. It adds significant value beyond the schema's bare properties.

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's purpose: 'Set articulation for notes — legato, staccato, or tenuto.' It specifies a verb ('set'), resource ('articulation for notes'), and enumerates the exact types, making it distinct from siblings like mcp_opendaw_apply_articulation.

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 for when to use each articulation (e.g., 'Use for smooth string lines...'), but does not explicitly differentiate from sibling tools or state when not to use this tool. It lacks alternatives, but the within-tool guidance is strong.

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