Skip to main content
Glama

mcp_opendaw_create_pedal_point

Create sustained bass notes under changing chords to build harmonic tension and release, using customizable pitch, chord progressions, and timing.

Instructions

Create a pedal point — sustained bass tone under changing chords.

A foundational technique in film scoring (Hans Zimmer drones), organ preludes (Bach), and rock ballads. A single low note sustains (or retriggers) while chords change above it, creating harmonic tension and release. The pedal anchors the harmony while the chords create movement.

pedal_pitch: Sustained bass note (default 36 = C2, low and powerful). chord_pattern: Comma-separated chord names (e.g. "Cm,Ab,Eb,Bb"). Supports: maj, min, m7, maj7, dom7, sus2, sus4, dim, aug. bars_per_chord: Bars each chord lasts (1-8, default 1). beats_per_bar: Time signature beats (3/4=3, 4/4=4, 6/8=6, default 4). pedal_velocity: Velocity of pedal note (0-1, default 0.75). chord_velocity: Velocity of chord notes (0-1, default 0.6). chord_octave: Octave for chord notes (1-8, default 4 = C4 range). retrigger_pedal: If true, pedal re-triggers at each chord change. If false, one long sustained note for the entire duration. unit_index: AU index with note track (-1 = find first AU with note tracks). track_index: Note track index within the AU. start_beat: Position in beats where the pedal point begins.

Returns notes created, chord count, pedal duration.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
start_beatNo
unit_indexNo
pedal_pitchNo
track_indexNo
chord_octaveNo
beats_per_barNo
chord_patternNoCm,Ab,Eb,Bb
bars_per_chordNo
chord_velocityNo
pedal_velocityNo
retrigger_pedalNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior3/5

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

No annotations provided, so description carries full burden. It explains the tool creates notes and returns a summary, but does not disclose whether it overwrites existing notes, requires specific track setup, or has performance implications.

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: a clear definition, musical context, then parameter details. It is somewhat verbose for the parameter section but remains readable and front-loaded.

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 covers input parameters well but lacks details on output format (beyond a brief mention) and error handling. No output schema is provided, and behavioral gaps (e.g., overlapping notes) remain unaddressed.

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

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description compensates thoroughly by explaining all 11 parameters with defaults, supported chord types, and behavioral options like retrigger_pedal. This adds significant meaning beyond the schema's bare titles.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a pedal point with a sustained bass tone under changing chords. It provides musical context but does not explicitly differentiate from sibling tools like create_ostinato or create_bassline, so sibling distinction is implicit.

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 gives context (film scoring, organ preludes, rock ballads) implying when to use it, but lacks explicit guidance on when not to use or alternatives. No mention of prerequisites or compared tools.

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