Skip to main content
Glama

create_drum_pattern

Generates and plays drum grooves—four-on-floor, breakbeat, shuffle, half-time, two-step, random, or custom patterns—with tempo, swing, volume, and effects controls.

Instructions

Play a drum groove: four_on_floor, breakbeat, shuffle, half_time, two_step, random, or a custom pattern.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_drum_pattern"
  }
}

Input Schema

NameRequiredDescriptionDefault
barsNoNumber of 4/4 bars (16 steps each)
seedNoRandom seed for a reproducible result; omit for a new one
swingNoDelay of off-beat 16ths; 0.33 = shuffle
tempoNoBeats per minute
customNoYour own pattern instead of pattern_type: lanes kick, snare, hat, open_hat, perc, one character per 16th step: X accent, x hit, o ghost, . rest. Example: {'kick': 'X...x...X...x...', 'snare': '....X.......X...'}
volumeNoLoudness, 0..1
effectsNoOptional effect chain
pattern_typeNofour_on_floor

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.1

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already establish that this is not read-only, not destructive, not open-world, and not idempotent. The description adds that it 'plays' a groove, implying an audible side effect, but does not explain playback behavior such as duration, concurrency, whether it replaces current playback, or other operational details.

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 a single front-loaded sentence that gets directly to the tool's purpose and options, with no filler. It is appropriately concise, though it could be organized slightly better to separate the preset list from the custom alternative.

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

Completeness3/5

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

The tool has 8 parameters, rich schema descriptions, annotations, and an output schema, so the description does not need to carry all detail. Still, it omits sibling-tool differentiation and important behavioral context about what playback does, leaving meaningful gaps for an agent choosing among audio-generation tools.

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

Parameters3/5

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

Schema description coverage is high at 88%, so the schema already documents nearly all parameters in detail. The description names the pattern_type options and contrasts them with a custom pattern, but that information is largely already present in the schema enum and custom parameter description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: 'Play a drum groove', and enumerates supported preset patterns plus a custom option. It is clear what the tool does, though it does not explicitly distinguish itself from sibling rhythm/synthesis tools such as create_generative_rhythm.

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

Usage Guidelines3/5

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

The description implies usage for playing drum grooves and notes the choice between a preset pattern and a custom pattern. However, it gives no explicit guidance on when to use this tool instead of sibling tools, nor any when-not conditions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.