Skip to main content
Glama

arrange

Copy a Session clip onto the Arrangement timeline at a precise beat, turning a session idea into an arrangement while preserving the original clip.

Instructions

Copy a Session clip onto the Arrangement timeline at a beat position.

A copy, not a move: the Session clip stays in its slot and the two are separate
clips afterwards, so editing one leaves the other alone. This is how a Session
idea becomes an arrangement, and how clip automation written by write_automation
reaches the Arrangement timeline.

Returns:
    Dictionary with the placement status, the destination track, and the
    Arrangement clip count before and after.

Note:
    Call it once per placement. Repeating the same call adds another copy at the
    same beat rather than replacing the first, so a retry after an unclear result
    needs the clip count in this answer checked first.

    Use create_clip and write_clip_notes to build the source clip, and
    set_arrangement_time then play to hear where it landed.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slotYesClip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down.
trackYesTrack index in song.tracks, counted from 0.
at_beatYesWhere the copy starts on the Arrangement timeline, in beats from the start of the song. Fractional beats are accepted.
to_trackNoTrack index to place the copy on. Omit to use the source track, which is the usual case. A MIDI clip needs a MIDI destination.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed4 schema fields changedv0.1.1
    • addedInput schema / properties / at_beat / description
      Added value: +"Where the copy starts on the Arrangement timeline, in beats from the start of the song. Fractional beats are accepted."
    • addedInput schema / properties / slot / description
      Added value: +"Clip slot index in track.clip_slots, counted from 0. A slot index is the scene the clip sits in, so slot 2 is the third scene down."
    • addedInput schema / properties / to_track / description
      Added value: +"Track index to place the copy on. Omit to use the source track, which is the usual case. A MIDI clip needs a MIDI destination."
    • addedInput schema / properties / track / description
      Added value: +"Track index in song.tracks, counted from 0."
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

The description goes well beyond the annotations by explaining the copy-not-move semantics, that editing one clip leaves the other alone, that repeated calls add another copy rather than replacing the first, and that the response includes clip counts for verification. This complements the idempotentHint=false annotation with concrete behavioral detail.

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?

The description is front-loaded with the core operation, then adds behavioral nuance, return-value context, and a practical note. Every sentence earns its place; there is no filler or redundant restatement of the schema.

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?

Together with the rich input schema and the presence of an output schema, the description covers the operation, its non-idempotent behavior, prerequisites via create_clip and write_clip_notes, and a verification strategy using the returned clip count. Nothing critical is missing for correct invocation.

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 coverage is 100% and each parameter already has a clear description. The tool description reinforces at_beat and to_track indirectly but adds no new parameter-level meaning beyond the schema, so the baseline of 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 states a precise operation: 'Copy a Session clip onto the Arrangement timeline at a beat position.' It immediately clarifies this is a copy, not a move, and explains its role in turning Session ideas into arrangement material, distinguishing it from related clip tools like create_clip and write_clip_notes.

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 gives clear when-to-use context: to bring a Session clip into the Arrangement timeline and to get write_automation output there. It also provides a workflow with create_clip, write_clip_notes, set_arrangement_time, and play. It does not explicitly name alternatives or when-not-to-use conditions, so it misses the top bar by a small margin.

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

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/romanstark/live-maestro'

If you have feedback or need assistance with the MCP directory API, please join our Discord server