Skip to main content
Glama

mcp_opendaw_swap_sections

Exchange two sections of a musical arrangement to quickly restructure a song. Swap any two time ranges, moving content and shifting adjacent parts automatically.

Instructions

Swap two sections of the arrangement — exchange their positions on the timeline.

Exchanges all note/audio content between two time ranges, moving section A to where section B was and vice versa. Useful for song structure experimentation: try chorus before verse, swap bridge with solo, reorder sections without manual cut/paste.

Both sections can be different lengths — the swap preserves each section's content and shifts everything accordingly. If sections are adjacent, it's a simple swap. If there's a gap between them, the gap content stays in place.

Args: section1_start: Start beat of first section section1_end: End beat of first section section2_start: Start beat of second section (must be > section1_end) section2_end: End beat of second section unit_indices: Comma-separated unit indices to process ("" = all units)

Returns: JSON with sections_swapped, notes_moved per unit, section sizes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
section1_endYes
section2_endYes
unit_indicesNo
section1_startYes
section2_startYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior5/5

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

No annotations are provided, so the description fully bears the burden of transparency. It explains that content is exchanged, different lengths are handled, and gaps between sections stay in place. This gives a clear behavioral model without requiring annotations.

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 paragraphs and an explicit Args section, but it is somewhat lengthy. It could be slightly more concise while retaining clarity.

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 complexity (swapping with length differences, gaps, units), the description covers all key behaviors and even mentions return format. An output schema exists, but the description still adds value by explaining sections_swapped, notes_moved, and section sizes.

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?

Schema description coverage is 0%, but the description includes an 'Args' section that explains all five parameters clearly: section1_start/end, section2_start/end, and unit_indices. This adds essential meaning beyond the bare schema titles.

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 swaps two sections of the arrangement by exchanging their positions. It uses specific verbs ('swap', 'exchange') and resources ('sections', 'arrangement'), and distinguishes from sibling tools like move_section or reorder_sections by focusing on a reciprocal exchange.

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 explicit usage context: 'Useful for song structure experimentation' and gives examples like swapping chorus before verse. However, it does not explicitly state when not to use the tool or mention alternative tools like reorder_sections for multi-section reordering.

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