Skip to main content
Glama

mcp_opendaw_add_neighbor_tones

Add upper or lower neighbor tones to ornament sustained notes by stepping away one scale step and returning. Embellish melodies with diatonic neighbor tones for expressive phrasing.

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

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

No annotations are provided, so the description carries the full burden. It explains the algorithmic structure (splitting the original note into three parts: first part, neighbor, return), with precise details on how the neighbor is placed. It discloses that short notes are skipped (min_duration_beats parameter) and that the default neighbor velocity is softer than the main note. It also explains the cross_track parameter for preserving original notes. This is comprehensive behavioral disclosure.

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: a one-sentence summary, a musical explanation, a structural outline, a comparison to siblings, genre examples, and then a clearly formatted parameter list. Every sentence adds value—no fluff, no repetition. It front-loads the core purpose and immediately differentiates from related tools. The parameter descriptions are concise yet informative, using consistent formatting.

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?

The description is exhaustive for a tool with 11 parameters and no schema descriptions. It covers the musical theory, the splitting algorithm, all parameter constraints, defaults, and even cultural context (Bach, jazz, country, classical). The output schema exists, so return values need not be explained. The description leaves no significant gaps for an agent to understand and invoke the tool correctly.

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 coverage is 0%, meaning no parameter descriptions in the JSON schema. The description compensates fully by explaining every parameter in detail, including valid ranges, defaults, and musical implications. For example, neighbor_fraction is described as '0.1-0.5, default 0.25' with guidance on subtle vs prominent effects. neighbor_offset: '0.1-0.9, default 0.5' with examples (0.15 near start, 0.5 middle, 0.85 near end). direction: explains 'upper', 'lower', 'alternating' with context. This adds immense value beyond the schema.

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 begins with a clear verb+resource: 'Add upper/lower neighbor tones to embellish existing notes.' It immediately distinguishes neighbor tones from passing tones by explaining that neighbor tones ornament a single sustained note while passing tones connect two different notes. This explicitly differentiates it from its sibling tools like mcp_opendaw_add_passing_tones, establishing a unique purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly contrasts neighbor tones with passing tones ('Unlike passing tones which connect two different notes...'), and positions it as the third of four classic non-chord tone techniques (passing tones, suspensions, neighbor tones, anticipation). This provides clear guidance on when to use this tool versus alternatives. It also lists genres where neighbor tones are used, helping the agent choose appropriately.

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