Skip to main content
Glama

mcp_opendaw_create_chop

Slice a sequence of pitches into equal segments and rearrange them using modes like reverse, stutter, shuffle, ping-pong, or gate to create rhythmic chops for hip-hop, EDM, or glitch effects.

Instructions

Create a chop — slice source pitches into segments and rearrange them.

The quintessential hip-hop/EDM sampling technique: take a sequence of pitches, cut it into equal segments, then rearrange (reverse, stutter, shuffle, ping-pong). Think Dilla chops, Madlib sample flips, Virtual Riot bass chops, or glitch-hop stutter effects. Each segment becomes a self-contained musical cell.

pitches: Comma-separated MIDI pitches to use as source material (e.g. "60,62,64,67"). chop_mode: How to rearrange segments — "reverse" (play segments backwards), "stutter" (repeat each segment N times — glitch/stutter effect), "shuffle" (random segment order, seeded), "ping-pong" (forward then backward — ABBA pattern), "gate" (silence every other segment — chopped break feel). segment_beats: Duration of each segment in beats (0.25-4, default 0.5 = 8th note). stutter_count: For stutter mode, times to repeat each segment (2-8, default 2). octave_shift: Shift all pitches by N octaves (default 0). -1 = down an octave for bass chops. velocity_variation: Vary velocity between segments (0-0.5, default 0.2). Adds human feel. reverse_pitch_in_segment: If true, reverse pitch order within each segment (inner chop). unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the chop begins. velocity: Base velocity (0-1, default 0.9). seed: Random seed for reproducibility.

Returns notes created, segment count, mode used.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
seedNo
pitchesNo60,62,64,67,60,64,62,60
velocityNo
chop_modeNoreverse
start_beatNo
unit_indexNo
track_indexNo
octave_shiftNo
segment_beatsNo
stutter_countNo
velocity_variationNo
reverse_pitch_in_segmentNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full burden. It discloses that the tool creates new notes and modifies their arrangement, but doesn't explicitly state whether it modifies existing notes or works non-destructively. The return value is mentioned, but permissions or side effects are not addressed.

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 clear summary, contextual explanation, and parameter list. It is front-loaded with the main purpose. A few sentences could be trimmed, but overall it is appropriately sized for a complex tool.

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 12 parameters, no annotations, and presence of output schema, the description provides a solid understanding of the tool's functionality, including modes, parameters, and return values. It lacks discussion of prerequisites or error cases, but is sufficient for an agent to use the tool effectively.

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%, so the description compensates by explaining each parameter in detail with musical context (e.g., chop_mode explanations, segment_beats range, stutter_count range). It adds meaning beyond the schema property names, though some parameter details (like exact format for pitches) could be clearer.

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 chop — slice source pitches into segments and rearrange them.' It uses a specific verb-resource pair and distinguishes this tool from siblings by emphasizing the hip-hop/EDM sampling technique with references to Dilla, Madlib, etc.

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 context for when to use this tool ('quintessential hip-hop/EDM sampling technique') with examples of musical applications. However, it does not explicitly state when not to use it or mention alternative tools (e.g., create_stutter for stutter-only effects).

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