Skip to main content
Glama

create_drum_pattern

Create drum patterns in REAPER from step-sequencer shorthand. Specify drum characters, track, and start position to generate a MIDI item.

Instructions

Create a drum pattern from step-sequencer shorthand.

Each line of pattern is one drum lane. Characters map to GM drums: k=kick, s=snare, h=hi-hat closed, o=hi-hat open, c=crash, r=ride, t=mid tom, l=low tom, i=high tom, p=clap, b=rimshot. . or space = rest. Any unknown character is ignored.

Example — standard 16-step rock beat:

k...k...k...k...
....s.......s...
h.h.h.h.h.h.h.h.

Defaults: 16 steps per bar = 1/16-note grid. channel=9 = GM drum channel. Pass item_index=-1 to auto-create a new MIDI item positioned in the project at start_qn (e.g. bar 5 in 4/4 = start_qn=16.0). Building a multi-section arrangement on one track? Call this once per section with item_index=-1 each time and increasing start_qn — each call creates its own non-overlapping item at the right place, it does NOT append to a previous item.

Returns the item index and number of notes inserted.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
channelNo
patternYes
start_qnNo
velocityNo
bar_countNo
item_indexNo
track_indexYes
steps_per_barNo
Behavior4/5

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

No annotations are provided, so the description carries full burden. It discloses all key behaviors: creates MIDI items on drum channel 9, returns item index and note count, does not append to previous items, and ignores unknown characters. Could mention whether previous items are overwritten, but overall transparent.

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?

Well-structured with an example and separate sections for mapping and usage notes. Slightly lengthy but each sentence adds value. Front-loaded with the core concept.

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?

For 8 parameters and no output schema, the description covers pattern input, defaults, return value, and multi-section behavior. Lacks details on velocity/bar_count but these are intuitive. Completeness is high given context.

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?

With 0% schema description coverage, the description fully compensates by explaining pattern syntax in detail with character mapping, default values for channel, velocity, bar_count, steps_per_bar, and the special item_index=-1 usage. Adds meaning 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 the tool creates drum patterns from step-sequencer shorthand, specifying characters for GM drums and providing an example. It distinguishes itself from sibling tools like midi_insert_note by offering a dedicated shorthand syntax.

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

Usage Guidelines5/5

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

Explicit guidance is given for multi-section arrangements: use item_index=-1 and increasing start_qn for non-overlapping items. The description also explains that unknown characters are ignored, aiding correct usage.

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/xDarkzx/Reaper-MCP'

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