Skip to main content
Glama

mcp_opendaw_create_pan_sweep

Create panning automation sweeps to move audio signals from left to right or vice versa over time, with customizable start/end positions, duration, and curve.

Instructions

Create a panning automation sweep — move signal from left to right (or vice versa) over time.

Classic stereo movement technique for intros, guitar solos, EDM builds, and section transitions. Creates panning automation events on the AU's panning parameter, sweeping from one position to another. Uses linear curve by default (panning is already psychoacoustic, exp not needed).

unit_index: AU index. start_beat: Start position in beats. duration_beats: Sweep length in beats (default 8 = 2 bars). start_pan: Starting pan position -1.0 (full left) to 1.0 (full right). Default -1. end_pan: Ending pan position -1.0 to 1.0. Default 1 (full sweep L→R). curve: "linear" (default — even stereo movement), "exp" (accelerating), "log" (decelerating). steps: Number of automation points (default 24 = smooth).

Returns events created, pan range, and preview.

Examples: create_pan_sweep(unit_index=0, duration_beats=16) → 16-beat full L→R pan sweep, linear create_pan_sweep(unit_index=2, start_pan=0.5, end_pan=-0.5, duration_beats=4) → Quick 4-beat R→L sweep from half-right to half-left

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
curveNolinear
stepsNo
end_panNo
start_panNo
start_beatNo
unit_indexYes
duration_beatsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations, the description carries full burden. It explains that the tool creates automation events on the AU's panning parameter, defaults to linear curve, and clarifies psychoacoustic reasoning. Mentions shape options and steps. Lacks details on undoability or side effects, but sufficient for typical use.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Highly concise and well-structured: first line defines purpose, then usage context, parameter explanations, and examples. Every sentence adds value, with no redundancy. Front-loaded with key information.

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

Completeness5/5

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

Given the tool's moderate complexity (7 parameters), no annotations, and presence of output schema, the description covers all essential aspects: purpose, parameter semantics, return values (events created, pan range, preview), and examples. It is fully sufficient for correct invocation.

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?

Despite 0% schema description coverage, the description thoroughly explains each parameter: unit_index, start_beat, duration_beats, start_pan, end_pan, curve, steps, including ranges, defaults, and examples. This fully compensates for the schema's lack of descriptions.

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?

Description clearly states the verb 'Create' and the resource 'panning automation sweep', explains the effect of moving signal over time. It includes usage contexts (intros, guitar solos, EDM builds) and examples, distinguishing it from sibling tools like create_filter_sweep or create_volume_fade.

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?

Provides clear usage context: 'Classic stereo movement technique for intros, guitar solos, EDM builds, and section transitions.' However, it does not explicitly mention when not to use this tool or name alternatives, though the context implies its appropriateness.

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