Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_set_vertices

Replaces every vertex of a polygon or polyline with a new point list, adding or removing vertices to match. Returns read-back points and area changes for validation.

Instructions

Replace every vertex of one polygon or polyline with a new point list.

Changes the document; one revertible step (vw_revert_last restores the previous vertices). Works the same for both object types (the plain vs.SetPolyPt silently does nothing on polylines). Use vw_move_objects to shift a shape unchanged. Returns {points (read back), area_before, area_after, applied, warning?}; applied is false when Vectorworks did not take every point.

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": {
      "uuid": "<uuid>",
      "points": "<points>"
    },
    "name": "vw_set_vertices"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidYesUUID of the polygon or polyline (from vw_find_objects, vw_get_selection or vw_export_geometry).
pointsYesThe complete new vertex list, [[x, y], ...] in document units; vertices are added or removed to match its length.
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.
arc_radiiNoPolylines only: one radius per point in document units, used for type 4 (radius) vertices. Default: none.
vertex_typesNoPolylines only: one type per point, 0 corner, 1 bezier, 2 cubic, 3 arc, 4 radius. Default: all corners. Ignored for polygons.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.1.1
    • addedInput schema / properties / arc_radii / description
      Added value: +"Polylines only: one radius per point in document units, used for type 4 (radius) vertices. Default: none."
    • 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 / points / description
      Added value: +"The complete new vertex list, [[x, y], ...] in document units; vertices are added or removed to match its length."
    • addedInput schema / properties / uuid / description
      Added value: +"UUID of the polygon or polyline (from vw_find_objects, vw_get_selection or vw_export_geometry)."
    • addedInput schema / properties / vertex_types / description
      Added value: +"Polylines only: one type per point, 0 corner, 1 bezier, 2 cubic, 3 arc, 4 radius. Default: all corners. Ignored for polygons."
  2. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only declare readOnlyHint=false and destructiveHint=false; the description adds that the edit is one revertible step and that a plain vs.SetPolyPt silently no-ops on polylines. It further discloses the applied=false failure mode and an optional warning, which an agent needs in order to detect partial success.

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?

The operation and its revertibility are front-loaded, and the return shape sits last where it belongs. The vs.SetPolyPt aside is a slightly dense insertion but earns its place by explaining why this tool exists rather than the native call.

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 five parameters and no output schema, the description must carry the return contract, and it does: points read back, area_before, area_after, applied and an optional warning. Combined with the revert semantics and document scoping, nothing an agent needs to call this safely 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 uuid, document, arc_radii and vertex_types are already fully documented in structured fields. The description only reinforces that the point list is complete and that vertex counts change to match its length, which the schema already says, so it adds little beyond the baseline.

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?

"Replace every vertex of one polygon or polyline with a new point list" gives a precise verb, resource, cardinality (one object) and scope (every vertex). It is immediately distinguishable from vw_move_objects, which the description names as the shape-shifting alternative.

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?

It states when to use this instead of the closest sibling ("Use vw_move_objects to shift a shape unchanged") and names the undo path (vw_revert_last) for reversal. It also notes the tool works identically for polygons and polylines, removing a likely point of hesitation before invocation.

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