Skip to main content
Glama

mcp_opendaw_create_psytrance_arrangement

Generates a 145 BPM psytrance arrangement with drums, rolling bassline, hypnotic lead, and atmospheric pads in F minor.

Instructions

Create a psytrance arrangement — 145 BPM hypnotic Goa/psychedelic.

Psytrance (psychedelic trance) is a subgenre of trance born in Goa, India (early 1990s) and developed in Israel, Europe. Key:

  • 145-150 BPM, 4/4 time, driving and hypnotic

  • Rolling bassline: 16th notes with a specific "k-b-k-b" pattern (kick on downbeat, bass on offbeat, creating a rolling feel)

  • Layered percussion: tight hats, snare rolls, shakers

  • Hypnotic lead: repeated motifs, evolving filter sweeps

  • FM synth sounds, alien textures, sci-fi atmosphere

  • Often in F minor or E minor

Creates 4 tracks:

  1. Drums (track_index): Kick on every beat, snare on 2&4, tight 16th hats, shaker pattern, snare roll at end of phrases

  2. Bass (track_index+1): Rolling 16th bassline — kick-aligned bass notes with offbeat syncopation, creating the psytrance "gallop" feel

  3. Lead (track_index+2): Hypnotic repeated motif with filter sweep simulation (velocity variations), octave jumps

  4. Atmosphere (track_index+3): Sparse sustained notes, sci-fi pad-like textures on bar starts

Default key: F minor.

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 full burden. It details the 4 tracks created and their roles, but does not state if existing content is overwritten, required permissions, or response behavior. Decent but not comprehensive.

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 lengthy but well-structured: purpose first, then genre explanation, then track details. Could be slightly more concise, but the information is relevant and organized.

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 complexity (psytrance genre, 4 tracks), the description covers genre, structure, and track details comprehensively. Output schema exists, so return values are likely handled. Adequate for agent understanding.

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 coverage is 0%, so description must compensate. It adds context for bpm, bars, key_root, and track_index, but ignores unit_index and start_beat. Partial compensation, not full parameter clarity.

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 the verb 'Create' and resource 'psytrance arrangement', with specific genre details (BPM, key, track structure). It distinguishes from sibling tools like create_trance_arrangement by focusing on psytrance characteristics.

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 use for psytrance generation and details the output, but does not explicitly state when to use this tool versus alternatives (e.g., create_trance_arrangement). No exclusions or when-not guidance provided.

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