Skip to main content
Glama

mcp_opendaw_create_funk_arrangement

Creates a full funk arrangement with funky drummer, slap bass, scratch guitar, and horn stabs across four tracks. Builds a vamp-based groove at your chosen tempo and key.

Instructions

Create a full funk arrangement — funky drummer + slap bass + scratch guitar + horn stabs across 4 tracks.

James Brown / Parliament-Funkadelic style funk — vamp-based, not chord-progression-based:

  • Track 0: Drums — "Funky Drummer" pattern (Clyde Stubblefield, most sampled break in history): syncopated kick with ghost notes, snare with strong ghost accents, hi-hat with 16th-note syncopation. The groove that built hip-hop.

  • Track 1: Bass — slap bass: thumb (root, low) + pluck (octave/fifth, high) alternating, with dead notes (ghost) for percussive attack. The signature Larry Graham technique.

  • Track 2: Guitar — "scratch guitar" / "chank": 16th-note muted strumming on a single chord, with accents on specific 16ths. The rhythmic glue that makes funk tick — Niles Rodgers style.

  • Track 3: Horns — stabs: short, tight horn hits on the "and" of beats, responding to the vocal/instrumental lead. Brown-style section horn hits.

At 100 BPM (default), this creates the classic funk pocket — not too fast, deep in the groove. The vamp (one chord groove, not progression) is the fundamental difference from all other arrangements: pop/rock/jazz change chords, funk stays on one and makes it groove. 16th-note syncopation is the rhythmic DNA — every instrument plays 16ths with different accent patterns.

bpm: Tempo (90-115, default 100 = classic funk pocket). bars: Arrangement length (4-16, default 8). Funk vamps can go long. root: Root note (D is a classic funk key — D minor/D dominant). octave: MIDI octave for bass (2 = D2=38, standard funk bass register). unit_index: AU index with note tracks. drum_track / bass_track / guitar_track / horn_track: Track indices.

Returns notes created per track and total.

Example: create_funk_arrangement(bpm=100, root="D", bars=8) create_funk_arrangement(bpm=108, root="G", bars=16)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
rootNoD
octaveNo
velocityNo
bass_trackNo
drum_trackNo
horn_trackNo
start_beatNo
unit_indexNo
guitar_trackNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations are provided, so the description carries the transparency burden. It discloses that it creates an arrangement across tracks, returns "notes created per track and total," and mentions requiring a unit_index with note tracks. However, it does not state whether existing notes are overwritten, whether it creates missing tracks, or any prerequisites beyond the unit_index reference.

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 (several paragraphs) but well-structured with bullet-style track breakdowns, param definitions, and examples. The front-loaded first sentence states the core purpose immediately. Some historical references are colorful but not essential; still, every paragraph contributes to understanding the style and parameters.

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?

Given the tool's complexity (4 tracks, 11 parameters, genre-specific behavior), the description is quite complete: it explains musical roles, defaults, ranges, and even provides example calls. The output schema exists, so detailed return-value documentation is not required. The main gaps are behavioral side effects and the two undocumented parameters, which prevent a perfect score.

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 input schema has 0% description coverage, so the description must compensate. It adds meaningful semantics for bpm, bars, root, octave, unit_index, and the four track indices, including ranges, defaults, and musical intent. However, it omits two schema parameters (velocity and start_beat), which are left undescribed.

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 opens with a specific verb and resource: "Create a full funk arrangement" across four named tracks (drums, bass, guitar, horns). It clearly distinguishes itself from other arrangement tools by emphasizing the vamp-based, one-chord funk style, explicitly contrasting with chord-progression-based genres.

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 gives clear usage context: it is for James Brown / Parliament-Funkadelic style funk, vamp-based rather than chord-progression-based, and contrasts with "all other arrangements" that change chords. It does not explicitly name alternative tools or state 'do not use when X', but the genre and stylistic guidance are enough to infer appropriate use cases.

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-ai/opendaw-mcp'

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