Skip to main content
Glama

mcp_opendaw_create_electronic_bass

Generate electronic bassline patterns for dance music genres like house, techno, DnB, dubstep, acid, and garage, with customizable root, octave, and bars.

Instructions

Create an electronic bassline pattern — genre-specific bass for dance music.

Electronic basslines are fundamentally different from melodic basslines: they're rhythmic engines that lock with the kick drum. Each genre has a characteristic bass technique that defines its sound.

bass_type: "house_offbeat" — House off-beat bass: sustained notes on the "&" of each beat (between kicks). The classic house bass that creates the "untz-untz-untz" feel. Frankie Knuckles / Detroit house. "techno_sub" — Techno sub-bass: one long sustained root per bar, minimal. Pure low-end energy. Berlin techno / Marcel Dettmann. "dnb_reese" — DnB Reese bass: sustained note on beat 1, then syncopated stabs on the "e" and "a" of beats 2-4. Dark, detuned. Noisia. "dubstep_wobble" — Dubstep wobble: quarters on 1+3, wub pattern on 2+4 with repeated 16ths and fifth movement. Skrillex / Excision. "acid_303" — Acid 303: fast 16ths alternating root/octave with fifth drops. TB-303 squelch. Phuture / Hardfloor. "garage_2step" — UK garage 2-step bass: notes on 1 and 2.66, ghost on 3.5. Bouncy, syncopated. MJ Cole / Disclosure.

bars: Pattern length (1-16). root: Root note name (C, C#, D, etc. or flats Db, Eb). octave: MIDI octave (2 = C2=36). velocity: Base velocity 0-1.

Returns notes created, bass type, and pitch info.

Example: create_electronic_bass(bass_type="house_offbeat", root="C", track_index=0) create_electronic_bass(bass_type="dnb_reese", root="A", track_index=1, bars=4)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
barsNo
rootNoC
octaveNo
velocityNo
bass_typeNohouse_offbeat
start_beatNo
unit_indexNo
track_indexNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

The description discloses return values ('notes created, bass type, and pitch info') but lacks information on side effects, permissions, or safety profile. No annotations are provided, so the description partially fulfills the transparency burden.

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 purpose, background, parameter details, return info, and examples. It is slightly verbose due to the detailed bass_type descriptions, but those provide valuable context.

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 description covers the purpose and core parameters well, but missing explanations for some schema parameters and lacks guidance on how this tool relates to sibling bass creation tools. An output schema exists but is not analyzed.

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?

The bass_type parameter is explained in exceptional detail with musical context, but other parameters (bars, root, octave, velocity) receive only brief description, and parameters like start_beat, unit_index, and track_index are not described at all despite being present in 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 it creates an electronic bassline pattern, explicitly distinguishes from melodic basslines, and provides genre-specific options that differentiate it from sibling tools like create_bassline or create_walking_bass.

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 electronic dance music genres through the bass_type examples, but does not explicitly state when to use this tool versus alternatives or provide when-not conditions.

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