Skip to main content
Glama

mcp_opendaw_create_phonk_arrangement

Generate a full drift phonk arrangement with Memphis-style drums, sliding 808 bass, and a repetitive cowbell melody in a minor key.

Instructions

Create a full drift phonk arrangement — 3 tracks: drums + 808 + cowbell lead.

Drift phonk (Kordhell, MC Slvr, LXST CXNTURY) is the TikTok-era evolution of Memphis rap — dark, distorted, high-energy, with signature elements:

  • 120-140 BPM, usually minor key

  • Memphis-style drums: punchy kick on 1 and 3, snare/clap on 2 and 4, fast 16th hats with occasional rolls, lo-fi texture

  • 808 bass with slides (glide between notes, sustained resonance)

  • Cowbell melody — the iconic phonk sound, catchy repetitive riffs in minor pentatonic, often detuned/dark

  • Sidechain feel — bass ducks when kick hits

  • Distorted, lo-fi aesthetic

Creates 3 tracks:

  1. Drums (drum_track): Memphis-style — punchy kick, clap on 2&4, 16th hats with rolls at phrase ends, occasional perc hits.

  2. 808 bass (bass_track): Sliding 808 with sustained resonance. Follows root with chromatic slides, octave drops, and gaps where drums fill. The glide is simulated by short overlapping notes at pitch transitions.

  3. Cowbell lead (cowbell_track): Repetitive minor pentatonic riff in high octave, catchy and driving. 1-bar or 2-bar cycle.

bpm: Tempo (110-150, default 130). bars: Arrangement length (4-32, default 8). root: Root note (default F = common phonk key). octave: MIDI octave for 808 (2 = C2=36).

Example: create_phonk_arrangement(bpm=130, root="F", bars=8) create_phonk_arrangement(bpm=140, root="D#", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoF
octaveNo
velocityNo
bass_trackNo
drum_trackNo
start_beatNo
unit_indexNo
cowbell_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

With no annotations, the description carries full behavioral disclosure burden. It describes what the tool creates (3 tracks, their roles, and style influences) and provides parameter defaults, but does not address side effects (e.g., overwriting tracks), prerequisites, or error handling, which are important for agent decision-making.

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 sections for genre notes, track details, and parameters. It front-loads the purpose. Some detail (e.g., listing all genre characteristics) could be trimmed, but overall it is efficient and informative for its complexity.

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?

Given the tool has 10 parameters and no annotations, the description is incomplete. It explains output (3 tracks) but leaves several parameters unexplained (velocity, track indices, start_beat, unit_index). The presence of an output schema reduces the need to describe return values, but the parameter gaps remain significant.

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 0%, so the description must compensate. It explains four parameters (bpm, bars, root, octave) with examples, but leaves six parameters (velocity, bass_track, drum_track, start_beat, unit_index, cowbell_track) undocumented. This partial coverage is insufficient for a tool with 10 parameters.

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 'Create a full drift phonk arrangement — 3 tracks: drums + 808 + cowbell lead,' specifying verb, resource, and genre. It distinguishes this tool from sibling arrangement tools by naming a specific genre (drift phonk) and its unique elements.

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 on when to use the tool (for creating a drift phonk arrangement) and lists genre characteristics, but does not explicitly state when not to use it or compare to alternatives. The sibling list includes many other arrangement tools, but the description makes the niche clear.

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