Skip to main content
Glama

mcp_opendaw_diatonic_transpose_notes

Transpose notes by scale steps (diatonic) to preserve key during sequence construction, modal interchange, and counterpoint writing.

Instructions

Transpose notes by scale steps (diatonic) instead of semitones (chromatic).

Moves each note up or down by N steps within the specified scale. Unlike transpose_notes (which shifts by fixed semitones), diatonic transpose preserves the scale — C major C→D = +1 step (2 semitones), E→F = +1 step (1 semitone).

Essential for: creating variations that stay in key, modal interchange, sequence construction (moving a motif up the scale), walking bass from scale degrees, and counterpoint writing.

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). steps: Number of scale steps to transpose. +1 = up one step, -1 = down one step, +3 = up a third, -5 = down a fifth. 0 = no change. root_note: Root note of the scale — C, C#, D, D#, E, F, F#, G, G#, A, A#, B. scale: Scale name — major, minor, dorian, phrygian, lydian, mixolydian, pentatonic_major, pentatonic_minor, blues, harmonic_minor, melodic_minor.

Returns per-track note counts transposed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
scaleNomajor
stepsNo
root_noteNoC
unit_indexNo
track_indexNo
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 provided, the description carries full burden. It explains the mechanics (moves notes by scale steps, preserves scale), gives examples, and states the return value. It does not explicitly mention that the operation modifies notes in place, but the behavior is implied and reasonably transparent.

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 efficient, starting with a clear verb and contrasting with siblings. The 'Essential for' section adds valuable context without being excessively verbose. Minor redundancy (e.g., examples already implied by parameter descriptions) keeps it from a perfect 5.

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 the tool's complexity, 0% schema coverage, and presence of an output schema, the description adequately covers purpose, parameters, behavior, and use cases. It distinguishes from a key sibling. It could mention the scope (all notes in specified region/unit/track) more explicitly upfront, but parameter descriptions cover that.

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 explain all parameters. It does so thoroughly: for 'steps' it gives examples (+1 up, -1 down, +3 third), for 'root_note' it lists all notes, for 'scale' it lists all scale names. Every parameter is well-documented beyond the schema's minimal type/default info.

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 transposes notes by scale steps (diatonic) and explicitly contrasts with the sibling tool transpose_notes (chromatic). It provides concrete examples like C→D and E→F, making the purpose unambiguous.

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 includes an 'Essential for:' list of use cases (e.g., creating variations that stay in key, modal interchange) and contrasts with chromatic transposition, guiding when to use this tool. However, it does not explicitly state when not to use it.

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