Skip to main content
Glama

mcp_opendaw_create_psytrance_arrangement

Create a full psytrance arrangement with drums, rolling bass, hypnotic lead, and atmosphere tracks. Deliver a driving 145 BPM Goa/psychedelic trance groove 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 the full burden. It discloses the generated musical content in detail (kick pattern, bassline syncopation, lead motifs, atmosphere textures) and default key, but omits side effects such as whether existing notes on the target tracks are overwritten, or if any prerequisites exist. This is a notable gap for a creation tool.

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 summary, bullet points on genre traits, and a numbered list of tracks. While the genre history adds length, it provides useful musical context and each section earns its place. Slightly verbose but not excessively so.

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 thoroughly covers the musical output and track structure, but falls short on explaining all parameters and their constraints. Since there is an output schema, return values are not required to be described, but the lack of parameter semantics for 4 of 7 parameters makes the tool less complete for correct invocation.

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 explains track_index usage (offsets for the 4 tracks) and implies bpm and key_root defaults (145 BPM, F minor). However, it does not explain bars, velocity, start_beat, unit_index, or their effect on the generated arrangement, leaving most parameters without semantic meaning.

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 tool's function: 'Create a psytrance arrangement' with explicit details on genre characteristics and the 4 tracks it creates (Drums, Bass, Lead, Atmosphere). It distinguishes this from sibling genre tools by specifying psytrance-specific elements like 145 BPM, rolling bassline, and hypnotic lead.

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 for when to use the tool: when creating a psytrance arrangement, with specific musical attributes and track layout. However, it does not explicitly mention alternatives or when not to use it, though the genre-specific name and content implicitly distinguish it from siblings like create_trance_arrangement.

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