Skip to main content
Glama

mcp_opendaw_create_notes_batch

Batch create multiple MIDI notes in a single call for melodies, chords, or arpeggios.

Instructions

Create multiple MIDI notes in a single call — batch creation for melodies, chords, arpeggios.

notes: JSON array of note objects, each with:

  • pitch (int): MIDI note number (60 = C4, 69 = A4)

  • start (float): beat position

  • duration (float): note length in beats

  • velocity (float, optional): 0.0-1.0, default 0.8

Example: '[{"pitch":60,"start":0,"duration":0.5},{"pitch":64,"start":0.5,"duration":0.5},{"pitch":67,"start":1,"duration":1}]'

All notes go into one region on the specified note track. If no region exists, one is created. Faster than calling create_note repeatedly — one round-trip, one editing.modify() block.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
notesYes
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

Without annotations, the description carries the full transparency burden. It discloses that all notes go into one region, creates a region if needed, and uses a single editing block. However, it omits details on how 'unit_index' and 'track_index' parameters affect behavior.

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 front-loaded with purpose, uses bullet points for clarity, includes an example, and is concise with no extraneous information.

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?

The description covers core functionality, usage guidance, and behavioral traits well. However, it omits explanations for two parameters, and doesn't mention error handling or limits on note count. Output schema exists, so return values are not needed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description must compensate but only details the 'notes' parameter (structure, optional fields, default velocity). It provides an example. The other two parameters ('unit_index', 'track_index') are not explained at all.

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 creates multiple MIDI notes in a single call, explicitly for batch creation of melodies, chords, and arpeggios. It distinguishes itself from the sibling tool 'create_note' by highlighting efficiency gains.

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 provides clear when-to-use guidance by contrasting with repeated calls to 'create_note', emphasizing round-trip efficiency. However, it lacks explicit when-not-to-use or alternative sibling tools for specialized patterns.

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