Skip to main content
Glama

mcp_opendaw_set_articulation

Apply legato, staccato, or tenuto articulation to notes, adjusting gap and duration to shape how notes connect in a track.

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

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

With no annotations, the description fully discloses behavior: it explains exactly how each articulation alters note durations, how staccato_ratio and micro_gap affect the result, what happens to the last note and chord notes, and the return value. This is exemplary transparency.

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 long but well-structured: opening statement, articulation definitions, parameter semantics, return note, and examples. Every section adds necessary value, and the most critical info appears early. No wasted words.

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?

For a 6-parameter mutation tool with no annotations, the description covers selection scope, per-articulation behavior, parameter defaults, edge cases, and return format. It is complete enough for an agent to invoke correctly without additional context.

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 carry the parameter burden. It does: all six parameters are explained with defaults, value ranges, and musical meaning (e.g., 'staccato_ratio: 0.5 = half the available time', 'micro_gap: PPQN gap to leave between notes'). This vastly exceeds schema-only information.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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' with explicit legato/staccato/tenuto variants. It is specific about the resource (notes) and operation, but it does not differentiate itself from the sibling tool mcp_opendaw_apply_articulation, so it misses full sibling differentiation.

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 rich usage context, including musical recommendations ('Use for smooth string lines...', 'Use for sustained passages...') and edge-case behavior (last note, chords). It does not explicitly state when to use this tool instead of alternatives, but the context is clear enough for selection.

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