Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_duplicate_layer

Copy a design layer and all its objects to create a variant for testing changes without touching the original; the duplicate keeps scale and layer-order position.

Instructions

Copy a design layer with all its objects, to try a variant without touching the original.

Changes the document: one new layer, one revertible step (vw_revert_last deletes the copy). The copy keeps the scale and is placed right after the source in the layer list; the active layer stays active. Use vw_create_layer for an empty layer. Returns {document, layer, source, objects, source_objects, after_source, scale, visibility, uuid_map when asked for}; objects below source_objects means not every object was copied.

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": {
      "source": "<source>",
      "name": "<name>"
    },
    "name": "vw_duplicate_layer"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesName for the new layer; must not exist yet.
sourceYesName of the existing design layer to copy.
documentNoName of the document this must run in, as vw_list_documents shows it (".vwx" may be left out) or its full path. If another document is active, nothing changes. Omit to act on whatever document is active.
uuid_mapNoTrue: also return `uuid_map` {source object uuid: copy uuid}, including objects inside groups. Default False.
visibilityNoVisibility of the copy: "visible", "hidden" or "gray". Default: the same as the source has now. Layers share coordinates, so a visible copy lies exactly on top of the original.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / document / description
      Added value: +"Name of the document this must run in, as vw_list_documents shows it (\".vwx\" may be left out) or its full path. If another document is active, nothing changes. Omit to act on whatever document is active."
    • addedInput schema / properties / name / description
      Added value: +"Name for the new layer; must not exist yet."
    • addedInput schema / properties / source / description
      Added value: +"Name of the existing design layer to copy."
    • addedInput schema / properties / uuid_map / description
      Added value: +"True: also return `uuid_map` {source object uuid: copy uuid}, including objects inside groups. Default False."
    • addedInput schema / properties / visibility / description
      Added value: +"Visibility of the copy: \"visible\", \"hidden\" or \"gray\". Default: the same as the source has now. Layers share coordinates, so a visible copy lies exactly on top of the original."
  2. Added

TDQS

A4.4/5.0
Behavior5/5

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

Goes well past the annotations: declares that the document changes by exactly one new layer, that the operation is a single revertible step recoverable via vw_revert_last, that scale is preserved, placement is right after the source, and the active layer is unchanged. That is precisely the mutation context an agent needs for a non-readOnly, non-destructive tool.

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?

Front-loads the action and intent, then the mutation/revert facts, then the alternative, then the return contract. The dense return-key list in one clause is slightly heavy but each sentence carries information the agent needs.

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?

With no output schema, the description takes on the return contract and does so explicitly, including the diagnostic hint that objects below source_objects means a partial copy. Combined with the mutation/revert disclosure, nothing essential for correct invocation 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 parameters are already documented, and the description adds little param-level syntax beyond tying uuid_map to the returned map. It does clarify return-field semantics (objects vs source_objects), but that is output meaning rather than input meaning, 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 and resource (copy a design layer with all its objects) plus the intent (try a variant without touching the original), and explicitly distinguishes itself from vw_create_layer. An agent can identify the tool without opening the 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?

Names the alternative (vw_create_layer) and the condition that selects it (empty layer), and gives the motivating use case. It does not spell out exclusions or prerequisites (e.g. what happens if the target name already exists beyond the schema note), so it falls short of a full when/when-not treatment.

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