Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_move_objects

Moves one or more Vectorworks objects by X/Y/Z offsets while preserving rotation; unknown UUIDs cancel the entire edit, and one revert step restores them.

Instructions

Move objects by an offset, keeping their rotation and everything else. All-or-nothing on unknown UUIDs. One revertible step: vw_revert_last moves them back (a plug-in regeneration between move and revert can leave an object off by a fraction of a unit). Returns {moved: n}.

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

Input Schema

NameRequiredDescriptionDefault
dxNoOffset along x in document units.
dyNoOffset along y in document units.
dzNoOffset along z in document units, for 3D objects. 0 keeps the height.
uuidsYesUUIDs of the objects to move; at least one. One unknown UUID moves nothing.
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 / 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 / dx / description
      Added value: +"Offset along x in document units."
    • addedInput schema / properties / dy / description
      Added value: +"Offset along y in document units."
    • addedInput schema / properties / dz / description
      Added value: +"Offset along z in document units, for 3D objects. 0 keeps the height."
    • addedInput schema / properties / uuids / description
      Added value: +"UUIDs of the objects to move; at least one. One unknown UUID moves nothing."
  2. Added

TDQS

A4.3/5.0
Behavior4/5

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

Adds real behavior beyond the annotations: all-or-nothing semantics on unknown UUIDs, single-step revertibility, the {moved: n} return shape, and the subtle drift caveat when a plug-in regenerates between move and revert. Missing only permission/authorization context and any note about very large selection sizes.

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?

Three short sentences, front-loaded with the action and its invariant, then atomicity, then the revert/return contract. No filler and no repetition of schema content.

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?

Though there is no output schema, the description supplies the return shape, failure semantics, and undo story, while the schema covers document/front-office requirements. An agent has everything needed to call this safely and interpret the result.

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 dx/dy/dz/uuids/document are already fully documented, including the 'one unknown UUID moves nothing' and front-document rules. The description adds no parameter-level meaning beyond that, 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 ('Move objects by an offset') plus the important invariant that rotation and other properties are preserved, which is exactly what distinguishes a move from a re-place/re-create operation.

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?

Explicitly names vw_revert_last as the undo path and frames the move as 'one revertible step', and the schema pushes the caller to pass document for writes. It does not, however, contrast against other spatial alternatives (e.g. re-inserting symbols) or state when not to use it.

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