Skip to main content
Glama
Keystone for Vectorworks

Keystone for Vectorworks

vw2d_draw

Draw exact 2D objects in Vectorworks, including polygons, arcs, dimensions, and text, with class/layer attributes and per-object deviation checks.

Instructions

Draw exact 2D objects (all or nothing, one undo step).

Each item has a "type" plus geometry; optional "class", "layer", "name", "attributes", "unit" override the call-level defaults:

  • polygon / polyline: {"points": [[x, y], ...], "relative": false, "holes": [[[x, y], ...]]}. relative=true: points after the first are offsets (exact decimal sums, like a Maßkette).

  • path (lines + true arcs): {"start": [x, y], "segments": [ {"line_to": [x, y]}, {"arc_to": [x, y], "center": [cx, cy], "direction": "ccw"|"cw"} | {"arc_to": [x, y], "through": [x, y]} | {"arc_to": [x, y], "radius": r, "direction": "ccw", "large": false}], "closed": true, "holes": [path or points]}

  • rect: {"corner": [x, y], "width": w, "height": h, "angle": 0} or {"p1": [x, y], "p2": [x, y]}

  • circle {"center", "radius"}; arc {"center", "radius", "start_angle", "sweep"} or {"start", "through", "end"}; oval {"center", "width", "height", "angle"}; line {"p1", "p2"}; locus {"point"}

  • text {"text", "position", "size" (pt), "font", "align" left|center|right, "valign" top|center|baseline|bottom, "angle"}

  • dimension {"p1", "p2", "offset", "orientation" horizontal|vertical|aligned}; chain_dimension {"points": [...], ...} attributes: pen, fill ("none" or "#rrggbb"), hatch (name), line_style, line_weight (mm), opacity; without any, everything is 'by class'. Every object needs a class (class_name or per item) unless allow_no_class=True. Returns each object's uuid and its exactness (deviation between request and what Vectorworks stored), plus any check issues involving the new objects.

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

Input Schema

NameRequiredDescriptionDefault
unitNodocument
checkNo
itemsYes
layerNo
attributesNo
class_nameNo
tolerance_mmNo
allow_no_classNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.3.3

TDQS

A3.6/5.0
Behavior4/5

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

The annotations already declare a non-readonly, non-destructive, closed-world operation, and the description adds meaningful behavior: all-or-nothing execution in one undo step, the class requirement unless allow_no_class=True, and returned exactness plus check issues. It does not contradict the annotations.

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 description is long but largely justified by the nested item grammar, and it is front-loaded with the core purpose. The bullet structure is efficient, though some dense inline examples and missing separation between call-level parameters reduce clarity slightly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex drawing tool with no output schema, the description explains the return values (uuids, exactness, check issues) and class/attribute behavior well. It is nearly complete for invocation, but the missing usage guidance and unclear tolerance_mm/check semantics leave gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 0% schema description coverage, the description carries most of the parameter burden and does so extensively for the complex items grammar, including geometry types, attributes, and per-item overrides. It also covers class_name, layer, attributes, unit, and allow_no_class, but leaves tolerance_mm and the exact role of check under-explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource: drawing exact 2D objects with all-or-nothing behavior. It is clear what the tool creates, but it does not explicitly distinguish itself from related siblings such as vw2d_preview, vw2d_edit, or vw2d_transform.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

It describes the operation and atomic undo behavior but gives no explicit when-to-use or when-not-to-use guidance. It never names alternatives like vw2d_preview or explains conditions for choosing this tool over editing, transforming, or previewing geometry.

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