Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_create_layer

Add a design or sheet layer to the open Vectorworks document, optionally setting its scale and making it active. Use it to organize drawings or prepare presentation sheets; nothing is drawn on the layer.

Instructions

Create a design layer or a sheet layer in the open document. Adds the layer only; nothing is drawn on it. For a sheet with a viewport and title block use vw_create_sheet instead. The user's active layer stays active unless activate=True. One revertible step: vw_revert_last deletes the layer. Returns {name, kind, active}.

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

Input Schema

NameRequiredDescriptionDefault
kindNo'design' for a model/drawing layer, 'sheet' for a presentation sheet layer.design
nameYesName of the new layer. Fails if a layer of that name exists.
scaleNoDesign layers only: scale denominator, for example 48 for 1/4" = 1', 100 for 1:100. Omitted: the document's default.
activateNoTrue makes the new layer the active layer. Default False keeps the user's active layer.
documentNoName of the document this call may change, as listed by vw_list_documents. If given and another document is in front, nothing changes and the call fails; use vw_switch_document first. Always pass it for writes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / activate / description
      Added value: +"True makes the new layer the active layer. Default False keeps the user's active layer."
    • addedInput schema / properties / document / description
      Added value: +"Name of the document this call may change, as listed by vw_list_documents. If given and another document is in front, nothing changes and the call fails; use vw_switch_document first. Always pass it for writes."
    • addedInput schema / properties / kind / description
      Added value: +"'design' for a model/drawing layer, 'sheet' for a presentation sheet layer."
    • addedInput schema / properties / name / description
      Added value: +"Name of the new layer. Fails if a layer of that name exists."
    • addedInput schema / properties / scale / description
      Added value: +"Design layers only: scale denominator, for example 48 for 1/4\" = 1', 100 for 1:100. Omitted: the document's default."
  2. Added

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare non-readonly, non-destructive, closed-world; the description adds real behavior beyond that – nothing is drawn on the new layer, the user's active layer is preserved unless activate=True, and the change is a single revertible step undone by vw_revert_last. It also supplies the return shape {name, kind, active} in the absence of an output schema. Only a minor gap remains (no mention of the failure mode when a layer name already exists, which lives in the schema).

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 sentences, each carrying a distinct fact: action, scope limit, alternative, side effect, reversibility, return value. Front-loaded with the core action and zero 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 5-parameter mutation tool with no output schema, the description covers the missing pieces an agent needs: what is not created, whose active layer changes, how to undo, and what is returned. The document-guard requirement is already fully specified in the schema.

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 description coverage is 100%, so the schema already explains kind, name, scale, activate, and the document guard. The description reinforces only 'activate' and does not touch scale or the document parameter, so it adds little beyond the structured fields. 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 ('Create a design layer or a sheet layer in the open document') and immediately scopes it against the sibling that does more ('For a sheet with a viewport and title block use vw_create_sheet instead'). An agent can distinguish it from vw_create_sheet and vw_duplicate_layer without opening 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit when-to-use plus the alternative: use this for a bare layer, use vw_create_sheet when a viewport and title block are wanted. It also names the reversal path ('One revertible step: vw_revert_last deletes the layer'), so the agent knows both the routing decision and the undo route.

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