Skip to main content
Glama

mcp_opendaw_create_bassline

Generate a bassline from a root note and rhythmic pattern in one call. Define the pattern using scale degrees, rests, ties, and octave shifts for efficient music production.

Instructions

Create a bassline from root note + rhythmic pattern — one call instead of 8-20 create_note calls.

Basslines use low octaves (default octave 2 = C2=36) and high velocity (default 0.9).

root: Root note name (C, C#, D, D#, E, F, F#, G, G#, A, A#, B or flats Db, Eb, Gb, Ab, Bb). pattern: Rhythmic pattern using scale degrees and special chars. Each step = one 16th note:

  • Numbers 1-7 = scale degree (1 = root, 5 = fifth, etc.)

  • 0 = rest

  • '-' = sustain previous note (tie)

  • '+' = octave up for next note

  • '_' = octave down for next note

  • Example: "1 - - - 5 - - - 1 - - - 4 - - -" = root-fifth-root-fourth bassline

  • Example: "1 0 1 0 5 0 5 0 1 0 1 0 3 0 3 0" = syncopated bass unit_index: AU index with a note track. track_index: Note track index within the AU. start_beat: Where the bassline starts (0 = bar 1). octave: MIDI octave for the root (2 = C2=36, typical bass range). velocity: Note velocity 0-1 (default 0.9 for strong bass). scale: Scale type for degree mapping (default "minor"). Same scales as create_melody.

Returns the total notes created and pitches used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rootYes
scaleNominor
octaveNo
patternYes
velocityNo
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

With no annotations, the description fully discloses behavior: bassline octave and velocity defaults, pattern notation with special characters, return value, and parameter defaults. It provides comprehensive transparency.

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 thorough with examples and parameter details, which adds length but remains front-loaded and efficient. Slightly long but acceptable given complexity.

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?

Given 8 parameters, no annotations, and an output schema, the description covers purpose, pattern syntax, defaults, and return value comprehensively. No missing context for agent decision-making.

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 has 0% description coverage, but the description explains each parameter in detail, including root note formats, pattern syntax with examples, and defaults for octave, velocity, scale, etc. It fully compensates for the schema gap.

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 first sentence clearly states the tool creates a bassline from root note and rhythmic pattern, and explicitly contrasts with multiple create_note calls, differentiating it from sibling tools.

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 implies usage for bassline creation efficiently, contrasting with create_note, but does not explicitly mention when not to use it or provide alternatives among other bass-related tools.

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