Skip to main content
Glama
Audionaut MCP Server

Audionaut MCP Server

Assemble arrangement

assemble

Builds an arrangement of the given duration from the project's regions, sequentially or at random (requires regions - e.g. from auto_edit).

Instructions

Builds an arrangement of the given duration from the project's regions, sequentially or at random (requires regions - e.g. from auto_edit).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>"
    },
    "name": "assemble"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoSelection mode (default sequential)
seedNoRandom seed for reproducible random mode
taskNoName of the task this edit is part of, e.g. "remove speech pauses". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step
trackNoTrack id (default 0)
projectYesPath to the .audium project package (absolute paths recommended)
crossfadesNoApply crossfades at joints (default true)
duration_secondsNoTarget duration (default 60)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.7
    • addedInput schema / properties / task
      Added value: +{
      +  "description": "Name of the task this edit is part of, e.g. \"remove speech pauses\". In the open app, all edits with the same task name become one undo step: keep the name for every call of the task and change it when the next task starts. Without a task name, all edits of this session share one step",
      +  "maxLength": 80,
      +  "type": "string"
      +}
  2. First observedv0.2.0

TDQS

A3.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It implies a mutation ('Builds') and names a prerequisite, but never states what happens to existing project content, whether regions are copied or consumed, whether an existing arrangement is overwritten, or what undo/authorization behavior applies.

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?

It is a single, tightly constructed sentence with the core purpose and prerequisite front-loaded. No sentence is wasted.

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 purpose, duration, mode, and the region prerequisite, which is enough to know broadly what the tool does. For a seven-parameter, unannotated mutation tool with no output schema, it omits behavioral consequences such as how existing arrangement content is affected, leaving a meaningful gap.

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 description coverage is 100%, so all seven parameters are already documented in the schema. The description only reiterates duration, sequential/random mode, and the region prerequisite, adding little semantic detail beyond structured fields; baseline 3 is appropriate.

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 uses a specific verb and resource ('Builds an arrangement') plus scope details (duration, source regions, sequential/random modes). Its parenthetical requiring regions from auto_edit implicitly distinguishes it from that sibling, which creates the source material.

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?

It clearly states the prerequisite that regions must exist and points to auto_edit as the way to produce them, giving useful workflow context. It does not, however, explain when to choose random versus sequential mode or when this tool should be preferred over alternatives, so it stops short of explicit selection guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.