Skip to main content
Glama

duplicate_to_arrangement

Copies a Session clip to the Arrangement on the same track at a specified song position in beats, so you can schedule where it plays.

Instructions

Copy a Session clip into the Arrangement, on the same track. Repeat the call for every place the clip should play, then switch_to_arrangement_view to look at the result.

Parameters:

  • track_index: The track holding the Session clip

  • clip_index: Its Session slot

  • destination_time: Song position in beats where the copy starts

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": {
      "track_index": "<track_index>",
      "clip_index": "<clip_index>",
      "destination_time": "<destination_time>"
    },
    "name": "duplicate_to_arrangement"
  }
}

Input Schema

NameRequiredDescriptionDefault
clip_indexYes
track_indexYes
destination_timeYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.1.1

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose that the copy lands on the same track and that destination time is in beats, but it says nothing about whether existing clips at that position are overwritten, whether automation/warp settings are duplicated, or how failures surface.

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?

Front-loaded one-sentence purpose, then a workflow directive, then a compact parameter list. Every line earns its place, and the parameter meanings are warranted given the bare schema.

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 output schema handles return values, and all parameters are explained, so the basics are covered. For a mutation tool with zero annotations, however, the description should at least note overwrite/conflict behavior and any preconditions on the Session clip.

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

Parameters4/5

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

With 0% schema description coverage, the description supplies meaning for all three parameters, including the critical unit clarification that destination_time is a song position in beats. It leaves indexing base (0- vs 1-based) and valid ranges unstated, so it does not fully close the gap but adds substantial value.

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?

States a specific verb and resource with scope: "Copy a Session clip into the Arrangement, on the same track." This distinguishes it from siblings like duplicate_scene, duplicate_track, and build_arrangement without needing to open any schema.

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?

Gives clear operational guidance: call it once per playback position, then use switch_to_arrangement_view to inspect the result. It does not state exclusions (e.g., when to prefer build_arrangement or create_clip instead), so it stops short of full when/when-not coverage.

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

Deploy Server

Other Tools