Skip to main content
Glama

drum_patterns

Generate electronic drum patterns by style or Euclidean rhythm to get role-based step grids, tempo, swing, fills, and production notes for composition.

Instructions

Drum pattern library for electronic music. Without arguments, lists the styles (techno_four, techno_rolling, techno_hypnotic, minimal_techno, dub_techno, hard_techno, acid_techno, detroit_techno, house_classic, deep_house, tech_house, afro_house, uk_garage, breakbeat, electro, drum_and_bass, dubstep, trap, ebm). With style, its grids per role, tempo, swing, production notes and the available fills. With euclid_hits, returns a Euclidean rhythm grid, e.g. 3/8 = tresillo.

Grid language (one string per role, 16 steps = one bar of 16ths): x hit · X accent · o ghost · . rest · 2 3 4 ratchet · ? 50 % chance · * 25 % chance ghost.

Parameters:

  • style: Pattern style (optional)

  • euclid_hits / euclid_steps / euclid_rotate: Euclidean rhythm (optional)

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": "drum_patterns"
  }
}

Input Schema

NameRequiredDescriptionDefault
styleNo
euclid_hitsNo
euclid_stepsNo
euclid_rotateNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden, and it does disclose the behavior of each mode and the shape of what comes back (grids per role, tempo, swing, production notes, fills). It never explicitly states that the tool has no side effects and does not create clips or patterns, which is the main residual gap for a no-annotation tool.

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 front-loaded by mode, then supplies the grid legend and parameters, which is a sensible order. The long style list and grid legend are load-bearing given a 0% schema coverage, though the closing parameter block partly restates what the prose above already established.

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?

An output schema exists, so return values need no explanation, yet the description still tells the agent what each mode yields. What remains incomplete for a 4-parameter generative-lookup tool is how the style and Euclidean parameter sets interact, and the meaning of rotation.

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 must compensate, and it largely does: it enumerates all 19 valid `style` values (absent from the schema as an enum) and explains the Euclidean trio with a worked example (3/8 = tresillo). However, `euclid_rotate` is never explained, and the relationship between `euclid_steps` (default 16) and bar length is only implied.

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?

The description names a specific resource (a drum pattern library) and enumerates its three modes of operation: no-args style listing, `style` lookup, and `euclid_hits` Euclidean generation. It is clearly a read-only reference lookup, which implicitly separates it from write-side siblings like write_drum_pattern, though it never names an alternative.

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?

Usage is stated precisely in terms of arguments: omit arguments to list styles, pass `style` for grids/tempo/swing/notes/fills, pass `euclid_hits` for a Euclidean grid. What is missing is guidance on combining modes (e.g. whether `style` and `euclid_*` can be used together) and any explicit exclusion against sibling tools.

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

Deploy Server

Other Tools