Skip to main content
Glama

mcp_opendaw_create_hardstyle_arrangement

Generate a hardstyle arrangement with four tracks: kick drums, reverse bass, screech lead, and stab chords, at 150 BPM in a minor key.

Instructions

Create a hardstyle arrangement — 150 BPM festival hard dance.

Hardstyle is a Dutch electronic dance genre characterized by:

  • Hard, distorted kick drum with a pitched tail (the signature sound)

  • Reverse bass (off-beat bass that "reverses" the kick pattern)

  • Screechy/sawtooth lead synth with wide unison

  • 150 BPM, 4/4 time

  • Aggressive, festival/headbanger energy

Creates 4 tracks:

  1. Drums (track_index): Hard kick on every beat, snare on 2&4, closed hats on offbeats, open hat occasionally

  2. Bass (track_index+1): Reverse bass pattern — bass on offbeats between kicks, creating the signature "boom-BM-boom-BM" feel

  3. Lead (track_index+2): Screechy sawtooth lead playing a minor melody with wide intervals and octave jumps

  4. Chords (track_index+3): Stab chords on beat 1 and 3, minor key

Default key: F minor (common hardstyle key).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bpmNo
barsNo
key_rootNoF
velocityNo
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?

With no annotations, the description carries the burden of behavioral disclosure. It reveals that four tracks are created with specific patterns and default key, but omits operational details such as overwrite behavior, track placement conflicts, return values, or required project state.

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 lead sentence, followed by genre context and a bulleted track breakdown. The genre education paragraph is somewhat extended, but the overall organization aids readability without excessive redundancy.

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

Completeness2/5

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

For a 7-parameter tool with no annotations and no output schema details, the description is incomplete. It explains the musical arrangement thoroughly but does not cover parameter semantics, side effects, prerequisites, or return behavior, leaving significant gaps for an AI agent.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/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 only indirectly references track_index and mentions musical traits like 150 BPM and F minor, but fails to explain parameters such as bars, velocity, start_beat, unit_index, or how bpm/key_root map to the described output.

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 hardstyle arrangement" with a specific verb and resource. It further distinguishes itself from sibling genre tools by detailing the hardstyle characteristics, BPM, and track structure, making its purpose unambiguous.

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 hardstyle creation but lacks explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like other genre arrangements, leaving the selection rationale to the genre context alone.

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