Skip to main content
Glama

duplicate

Copy a shot right after it or copy an entire scene after it, creating independent copies and returning new IDs in one undo step. Use add_shot for a new empty shot.

Instructions

Copy a shot (the copy goes right after it) or a whole scene (after it). Copies are separate: changing one never changes the other. Returns the new ids. One undo step for the person. For a new empty shot use add_shot.

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

Input Schema

NameRequiredDescriptionDefault
idYesShot id or scene id to copy.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.2
    • changedInput schema / properties / id / description
      Previous value: -"Shot id or scene id."New value: +"Shot id or scene id to copy."
  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?

Goes well past the annotations by disclosing placement (copy goes right after the source, or after the scene), independence of the copies, that new ids are returned, and that it's a single undo step. These are exactly the behavioral facts an agent needs before mutating project state.

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?

Five short clauses, each carrying distinct information (scope, placement, independence, return value, undo), with the core action front-loaded and the sibling pointer last. No filler.

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 one-parameter mutation tool with no output schema, the description covers scope, side effects, return value, and reversibility. Nothing an agent needs in order 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% and the single id parameter already documents accepting a shot or scene id. The description adds placement semantics but nothing new about the parameter itself, so the baseline of 3 is correct.

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) and resource (a shot or a whole scene), and explicitly separates itself from the add_shot sibling. An agent can decide between duplicating and creating from this one line.

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?

Names the key alternative (add_shot) with the condition that selects it: a new empty shot. It does not state any exclusions, such as when duplication is inappropriate, or mention other related tools like get_shot or delete.

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