Skip to main content
Glama
ameobius-ai

openDAW MCP

by ameobius-ai
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

mcp_opendaw_shift_mode

Transform notes from one scale to another by shifting only the differing degrees, preserving the tonic and melodic contour.

Instructions

Transform notes from one scale/mode to another, keeping the tonic.

Finds which scale degrees differ between from_scale and to_scale, then shifts ONLY the notes on those degrees by the interval difference. The tonic (degree 1) and unchanged degrees stay put — the transformation is surgical, not a blanket snap.

Examples: shift_mode(root_note="A", from_scale="minor", to_scale="dorian") → minor 6th (Ab) becomes major 6th (F#). A minor → A dorian. Only notes on degree 6 shift (+1 semitone). Everything else stays. shift_mode(root_note="E", from_scale="minor", to_scale="phrygian") → degree 2 (F#) becomes F natural (-1 semitone). E minor → E phrygian. shift_mode(root_note="D", from_scale="major", to_scale="mixolydian") → degree 7 (C#) becomes C natural (-1 semitone). D major → D mixolydian. shift_mode(root_note="C", from_scale="minor", to_scale="harmonic_minor") → degree 7 (Bb) becomes B natural (+1 semitone). C minor → C harmonic minor.

Unlike force_scale_notes (snaps to nearest scale tone — can change the melodic shape), shift_mode preserves the contour: notes that are already in the target scale don't move. Only the specific degrees that differ between the two scales are shifted.

Unlike reharmonize_progression (works on chord symbols), shift_mode works on individual notes in a region.

Args: unit_index: AU index (-1 = all AUs). track_index: Note track index (-1 = all note tracks). region_index: Region index (-1 = all regions on track). root_note: Tonic note (C, C#, D, ...). Stays the same for both scales. from_scale: Source scale name. to_scale: Target scale name. preserve_root: If True (default), never shift the tonic pitch class. If False, allow tonic to shift (rare, only for non-modal transformations).

Returns per-note shift details: which pitch classes moved, by how much, and total notes affected.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
to_scaleNodorian
root_noteNoC
from_scaleNominor
unit_indexNo
track_indexNo
region_indexNo
preserve_rootNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes

Tool Definition Quality

A4.7/5.0
Behavior4/5

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

The description discloses the surgical algorithm: only differing degrees shift by interval difference, tonic and unchanged degrees stay put. It explains preserve_root behavior and the return value. However, the first example contains a note-name error ('minor 6th (Ab)' should be F natural), which slightly undermines clarity.

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 structured with a summary, algorithm, examples, contrasts, args, and return. It is long but every section contributes; the typo is the only blemish.

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?

For a 7-parameter tool with output schema, the description covers the algorithm, examples, parameter meanings, and return format. It lacks an exhaustive list of valid scale names, but examples make it inferable. The typo in example one makes it slightly less complete.

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%, but the Args section fully explains each parameter: default meanings (-1 = all), root_note as pitch class, preserve_root semantics. This adds essential meaning beyond the bare 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 opens with a clear verb-object: 'Transform notes from one scale/mode to another, keeping the tonic.' It explicitly differentiates from force_scale_notes and reharmonize_progression, and the accompanying examples illustrate concrete musical transformations.

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?

It directly states when to use this tool over alternatives: unlike force_scale_notes (which snaps to nearest scale tone and changes contour), shift_mode preserves contour; unlike reharmonize_progression (works on chord symbols), shift_mode works on individual notes. This is explicit usage guidance.

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