Skip to main content
Glama

mcp_opendaw_create_four_on_floor

Create a four-on-the-floor drum pattern for house, techno, or disco. Specify floor type, pitches, velocity, and bar length to produce the beat.

Instructions

Create a four-on-the-floor pattern — the foundational beat of house, techno, and disco.

Four-on-the-floor: kick drum on every quarter note (beats 1, 2, 3, 4). This is the pulse that defined dance music from disco (1970s) through Chicago house (1980s) to Berlin techno and beyond. The variation comes from what happens BETWEEN the kicks: off-beat hi-hats, claps on 2+4, percussion, and swing.

floor_type: "classic_house" — Chicago/Detroit house: kick on every quarter, open hat on off-beats (the "&" of each beat), clap on 2 and 4. The Frankie Knuckles / Roland TR-909 sound. 1-bar cycle. "deep_house" — Deep house: kick on quarters, shuffled hats, rimshot on 2/4, sparse percussion on the "e" and "a". Soulful swing. Larry Heard / Kerri Chandler style. "techno" — Detroit/Berlin techno: relentless kick on quarters, 16th hats, industrial clap on 2+4, metallic percussion on off-beats. Driving, minimal. Jeff Mills / Surgeson. "disco" — 70s disco: kick on quarters, open hat on off-beats, tambourine 16ths, conga fills. Giorgio Moroder / Donna Summer "I Feel Love" feel. "tech_house" — Tech house fusion: kick on quarters, swung hats, clap on 2/4, occasional vocal-style percussion stabs. Groovy but driving. Solardo / Fisher style.

bars: Pattern length (1-16, 1 = one bar cycle). kick_pitch: MIDI pitch for kick (36 = C1). hat_pitch: MIDI pitch for closed hi-hat (42 = F#1). open_hat_pitch: MIDI pitch for open hi-hat (46 = A#1). clap_pitch: MIDI pitch for clap (39 = D#1). perc_pitch: MIDI pitch for percussion (75 = high wood block / rim). velocity: Base velocity 0-1. Claps -0.05, hats -0.15, open hats -0.1, ghost -0.3.

Returns notes created, floor type, and stroke breakdown.

Example: create_four_on_floor(floor_type="classic_house", track_index=0) create_four_on_floor(floor_type="techno", track_index=1, bars=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
velocityNo
hat_pitchNo
clap_pitchNo
floor_typeNoclassic_house
kick_pitchNo
perc_pitchNo
start_beatNo
unit_indexNo
track_indexNo
open_hat_pitchNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations provided, so the description carries full burden. It explains what the tool does, the pattern structure, and floor_type variations. It mentions return values (notes created, floor type, stroke breakdown). Lacks detail on side effects or authentication, but is fairly 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?

The description is long but well-structured: purpose, background, parameter explanations, and example calls. Could be slightly more concise, but all information is necessary and ordered logically.

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

Completeness5/5

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

Given 11 parameters, no annotations, and presence of output schema, the description covers tool purpose, all parameters with defaults, examples, and return description. It is comprehensive and leaves no major gaps.

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?

Schema coverage is 0%, so description adds all parameter meaning. It explains each parameter (floor_type, bars, kick_pitch, etc.) with defaults and examples. Adds musical context beyond parameter names, fulfilling the requirement completely.

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 it creates a 'four-on-the-floor pattern' and defines it explicitly. It lists five distinct floor types with musical context, differentiating from other drum pattern tools. The verb-object relationship is specific and unambiguous.

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 (foundational beats for house, techno, disco). It does not explicitly state when not to use it or name alternatives, but the context is strong enough for an agent to infer appropriate 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/AMEOBIUS-team/opendaw-mcp'

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