Skip to main content
Glama

mcp_opendaw_add_neighbor_tones

Add upper or lower neighbor tones to existing notes, splitting each note into original-neighbor-return for diatonic ornamentation. Embellish sustained notes with scale-based neighbor steps.

Instructions

Add upper/lower neighbor tones to embellish existing notes.

A neighbor tone is a non-chord tone that steps away from the main note by one scale step (up or down) and then returns. Unlike passing tones which connect two different notes, neighbor tones ornament a single sustained note.

Structure: [main first part] → [neighbor (dissonance)] → [main return]

The original note is split into three parts:

  1. First part: original pitch from start to neighbor_offset

  2. Neighbor: one scale step away, duration = neighbor_fraction of original

  3. Return: original pitch for the remainder

This is the third of the four classic non-chord tone techniques: passing tones, suspensions, neighbor tones, and anticipation.

Bach ornaments, jazz ballad fills, country chicken pickin', and classical cadenzas all use neighbor tones extensively.

Args: unit_index: Audio unit index track_index: Note track index region_index: Region index (-1 = first region) scale: Scale for diatonic neighbor step ("major", "minor", "dorian", "phrygian", "lydian", "mixolydian", "locrian", "harmonic_minor", "melodic_minor", "pentatonic", "blues", "chromatic") root: Root note for scale (C, C#, D, ... B) direction: Neighbor direction — "upper": step up from main note (most common) "lower": step down from main note "alternating": alternate upper/lower per note neighbor_fraction: Duration of neighbor as fraction of original note (0.1-0.5, default 0.25 = quarter of original). Smaller values create subtle ornaments, larger create more prominent embellishments. neighbor_offset: Position of neighbor within the note (0.1-0.9, default 0.5 = middle). 0.15 = near start, 0.5 = middle, 0.85 = near end. neighbor_velocity: Velocity of neighbor note (0-1, default 0.6 — softer than the main note, as is traditional for ornaments). min_duration_beats: Minimum note duration in beats to embellish (0.5-4.0, default 1.0). Short notes are skipped — ornaments need room to breathe. cross_track: If >= 0, place neighbors on this track index instead of source track (preserves original notes).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootNoC
scaleNomajor
directionNoupper
unit_indexYes
cross_trackNo
track_indexYes
region_indexNo
neighbor_offsetNo
neighbor_fractionNo
neighbor_velocityNo
min_duration_beatsNo

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 the full burden of behavioral transparency. It clearly explains the three-part note splitting structure, parameter effects (e.g., neighbor_offset position, min_duration_beats skipping short notes), and cross_track behavior that preserves original notes. However, it does not explicitly state the destructive/reversible nature of the default operation on the source track.

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-structured and front-loaded: a one-sentence summary, definition, structural breakdown, context, and then a thorough Args list. Every sentence serves a purpose—the music theory context and usage examples help the agent select the tool, while the Args section adds essential semantics not found in the schema. No redundancy or 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?

This is a complex 11-parameter tool with no annotations or schema descriptions. The description covers the algorithm, all parameter semantics, behavioral nuances (skipping short notes, cross-track placement), and musical context. Since an output schema exists, the lack of return-value explanation is acceptable. The description is complete enough for correct selection and invocation.

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?

The schema provides no parameter descriptions (0% coverage), but the description's 'Args' section compensates exceptionally well. Every parameter is explained with ranges, defaults, and musical reasoning (e.g., neighbor_velocity: 'default 0.6 — softer than the main note, as is traditional for ornaments'). This is more than sufficient for an agent to understand each parameter's meaning.

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 a specific verb+resource: 'Add upper/lower neighbor tones to embellish existing notes.' It further distinguishes itself from similar tools by explaining the difference from passing tones and positioning it as the third of four non-chord tone techniques, making it clear which sibling tool this is.

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 explicitly contrasts with passing tones ('Unlike passing tones which connect two different notes, neighbor tones ornament a single sustained note'), giving the agent a clear decision point among ornamentation tools. It also mentions musical styles (Bach, jazz, country) but does not explicitly state when not to use this tool or provide a direct comparison to say add_suspension.

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