Skip to main content
Glama

mcp_opendaw_create_soli

Create a homorhythmic unison passage (soli) with octave doublings from melody scale degrees and rhythm durations. Specify key, scale, voice count, and octave spread to generate the part across 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
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It explains that voices are created on consecutive tracks starting at track_index, and details the meaning of melody and rhythm patterns. It does not disclose whether tracks must already exist, what happens to existing data, or any side effects like track creation. This is adequate but not comprehensive.

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 relatively long but well-structured. It front-loads the definition and usage context, then provides parameter details. Every section adds value, though the parameter list could be condensed into a table. Overall, it is efficient for the complexity.

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 has 10 parameters and an output schema, the description explains the input parameters and the effect on tracks well. It does not describe the return value (e.g., created note events), but the output schema likely covers that. It is mostly complete for an agent to understand how to invoke the tool.

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?

With 0% schema description coverage, the description must explain parameters. It clearly explains melody_pattern (scale degrees), rhythm_pattern (durations), key_root, scale_name, voices (2-5), and octave_spread. However, it does not explain velocity, start_beat, unit_index, or track_index. This covers 6 of 10 parameters, adding significant 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 clearly states 'Create a soli — ensemble unison passage with octave doublings.' It defines the musical concept, distinguishes it from fugue and canon, and provides technical details about melody/rhythm patterns, scale degrees, and voicing. This leaves no ambiguity about the tool's purpose.

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 explains when a soli is common (jazz big band, orchestral tutti, rock/metal riffs) and contrasts it with fugue and canon. However, it does not explicitly state when to avoid this tool or compare it to sibling tools like create_fugue or create_canon, nor does it specify prerequisites.

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