Skip to main content
Glama

mcp_opendaw_create_soli

Generate a soli: ensemble unison melody doubled across octaves. Specify melody/rhythm patterns, key, scale, and voices to produce a homorhythmic passage on multiple tracks.

Instructions

Create a soli — ensemble unison passage with octave doublings.

A soli is a section where all instruments play the same melodic line in rhythmic unison, typically at different octaves. Common in jazz big band (Basie, Ellington, Herman), orchestral tutti passages, and rock/metal unison riffs. Unlike a fugue (polyphonic imitation) or canon (delayed entry), a soli is simultaneous and homorhythmic.

Melody pattern: space-separated scale degrees (0=root, 2=2nd, 4=3rd, -1=7th below, etc.). Negative = below root. Rhythm pattern: space-separated durations in beats. Key root: C, C#, Db, D, ... B. Scale: major, minor, dorian, phrygian, lydian, mixolydian, aeolian, locrian, harmonic_minor, melodic_minor, pentatonic_major, pentatonic_minor, blues, whole_tone. Voices: 2-5 (e.g. 3 = root octave + 1 octave up + 2 octaves up). Octave spread: how many octaves between lowest and highest voice.

Creates voices on track_index, track_index+1, ... track_index+voices-1.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
voicesNo
key_rootNoC
velocityNo
scale_nameNomajor
start_beatNo
unit_indexNo
track_indexNo
octave_spreadNo
melody_patternNo0 2 4 2 0 -1 0 3
rhythm_patternNo0.5 0.5 0.5 0.5 0.5 0.5 0.5 0.5

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 the full burden of behavioral transparency. It discloses the core behavior (unison melody with octave doublings), the pattern syntaxes, and the exact track placement ('Creates voices on track_index, track_index+1, ... track_index+voices-1'). However, it does not state whether existing notes are overwritten or whether target tracks must already exist, which is a minor gap.

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 definition, parameter explanations, and a clear side-effect note. The genre history and fugue/canon comparison are useful albeit slightly lengthy. Every section contributes to understanding, but it could be tightened without losing value.

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

Completeness3/5

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

This is a complex 10-parameter tool with no annotations, and while the description covers most core concepts, it omits explanations for unit_index, start_beat, and velocity. It also does not clarify what happens if melody and rhythm pattern lengths differ. The output schema exists, so return values are covered, but the missing parameter semantics are notable for a tool of this complexity.

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 description coverage is 0%, but the description compensates well by explaining most parameters: melody/rhythm patterns, key root, scale names, voices, octave spread, and track_index. It leaves velocity, start_beat, and unit_index undefined, so it is not fully complete, but the added detail is substantial.

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's purpose: 'Create a soli — ensemble unison passage with octave doublings.' It defines what a soli is, provides musical context, and explicitly distinguishes it from fugue and canon, which are sibling tools. The verb and resource are specific and 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 gives rich musical context (jazz big band, orchestral tutti, rock/metal riffs) and contrasts soli with fugue/canon, implying when to choose this tool over polyphonic or imitative alternatives. However, it does not explicitly name sibling tools or state clear 'use this when...'/'instead of...' exclusions, so it stops short of a 5.

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