Skip to main content
Glama

add_notes

Add MIDI notes to a clip by specifying pitch, start time, duration, velocity, and optional mute for each note.

Instructions

Add MIDI notes to a clip. notes: list of objects with fields: pitch (0-127), start (beats), duration (beats), velocity (0-127), mute (bool, optional). Example: [{"pitch": 60, "start": 0.0, "duration": 1.0, "velocity": 100}]

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
track_indexYes
slot_indexYes
notesYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior2/5

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

No annotations; description does not disclose whether notes are appended or overwritten, limits, or error behavior. Only basic addition is implied.

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?

Concise single sentence with an example. No unnecessary words, but could be better structured with separate sections.

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

Completeness2/5

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

Missing crucial context like append vs replace behavior, constraints on note properties, and error handling; insufficient given the tool's complexity and output schema.

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?

Schema coverage is 0%; description only explains the 'notes' parameter format but ignores required 'track_index' and 'slot_index', failing to compensate for low schema coverage.

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?

Clearly states it adds MIDI notes to a clip, distinguishing it from siblings like 'clear_notes' and 'get_notes'. Provides an example of the note object format.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives like 'clear_notes' or 'update_clip'. No mention of prerequisites or context for use.

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/juampicosta/ableton-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server