Skip to main content
Glama

mcp_opendaw_apply_articulation

Apply staccato, legato, tenuto, or accent articulation to notes by reshaping durations relative to grid position for deterministic phrasing changes.

Instructions

Apply articulation to existing notes — staccato, legato, tenuto, accent.

Reshapes note durations relative to their grid position to change phrasing character. Unlike velocity_curve (dynamics) or humanize (random), this applies deterministic duration ratios — the fundamental dimension of musical articulation.

unit_index: AU index. track_index: Note track index. region_index: Region index (-1 = all regions on the track). articulation: Articulation type:

  • "staccato" — shorten notes to fraction of their grid slot (default 50%)

  • "legato" — extend notes to nearly the next note's start (default 95%)

  • "tenuto" — hold notes to full grid slot (100%, no gap, no overlap)

  • "accent" — boost velocity on notes that fall on beat boundaries (downbeats) amount: Articulation depth 0-1 (default 0.5):

  • staccato: fraction of slot (0.3 = very short, 0.7 = moderate)

  • legato: overlap fraction (0.9 = near-full, 0.5 = half-fill)

  • tenuto: (unused, always full)

  • accent: velocity boost amount (0.3 = subtle, 1.0 = strong accent)

Returns per-region note counts and total notes reshaped.

Examples: apply_articulation(articulation="staccato", amount=0.3) # crisp, detached apply_articulation(articulation="legato", amount=0.95) # smooth, connected apply_articulation(articulation="accent", amount=0.8) # strong downbeat accents

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
amountNo
unit_indexNo
track_indexNo
articulationNostaccato
region_indexNo

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. It explains the deterministic nature, how each articulation reshapes durations, and what the tool returns. Missing potential side effects but still thorough.

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-structured with a summary, parameter details, and examples. It is appropriately sized for the tool's complexity, with no redundant sentences.

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

Completeness4/5

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

Given 5 parameters, no annotations, and output schema present, the description covers all major aspects: parameter meanings, articulation behaviors, and return value. Minor omissions like error handling, but sufficiently complete for an agent.

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

Parameters4/5

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

Schema coverage is 0%, so description compensates well. It explains each parameter with defaults, ranges (e.g., amount 0-1), and effects per articulation type. Examples further clarify usage.

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 applies articulations (staccato, legato, tenuto, accent) to existing notes, with a specific verb and resource. It distinguishes from siblings like velocity_curve and humanize by explaining it applies deterministic duration ratios.

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 this tool, including comparisons with alternatives (velocity_curve, humanize). It gives examples of articulation usage but does not explicitly state when not to use it, though the context is sufficient 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-team/opendaw-mcp'

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