Skip to main content
Glama

duplicate

Copy a track, scene, clip, or device directly after the original, or place a clip copy in an empty slot, and return the new copy's address.

Instructions

Copy a track, scene, clip or device; the copy goes right after the original (a clip can go to another empty slot with to_slot). Says the copy's address. One undo step.

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": {
      "target": "<target>"
    },
    "name": "duplicate"
  }
}

Input Schema

NameRequiredDescriptionDefault
targetYesWhat to act on: a track (t0, rA), a device (t0/d1, t0/d0/c1/d0), a clip (t0/s2 = the clip in slot 2 of t0) or a scene (s2).
to_slotNoFor a clip: copy into this empty slot. Empty: the next slot.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.6.1

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already flag this as a non-read-only, non-destructive, non-idempotent mutation, and the description adds meaningfully beyond them: the copy is inserted adjacent to the source, the operation is a single undo step, and the response reports the new address.

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?

Two tight sentences with the action and placement stated first and the alternate slot case parenthesized right after. Every clause carries information; the parenthetical is the only mild structural interruption.

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?

For a two-parameter local mutation with no output schema, the description covers what is copied, where the copy goes, the undo impact, and what the return value is (the copy's address). Nothing needed to call it correctly is missing.

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%, so both 'target' and 'to_slot' are already documented in the schema. The description only restates the clip/to_slot case ('copy into another empty slot'), adding no syntax or format detail beyond the structured fields, so the baseline 3 applies.

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 ('Copy') plus the exact resource set (track, scene, clip, device) and where the copy lands, which separates it from creation-style siblings like create_track or create_audio_clip without needing their schemas.

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 usage context: default placement is immediately after the original, and the one alternate case (a clip copied into a different empty slot via to_slot) is called out. It does not name when-not-to-use or a competing tool, so it stops short of full routing guidance.

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