Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_insert_truss_path

Builds a linked truss system along an L, U, rectangle, or polyline path from straight and corner symbols, fitting whole pieces per leg and placing it at a specified height.

Instructions

Build a truss shape (L, U, rectangle, any polyline with matching bends) from straights and corners, one chained system. Each leg takes as many whole straight pieces as fit; a corner piece sits at every interior point and takes its own length from both legs, so legs end up shorter than the path by the leftover gap (placed per fit). Pieces are linked in order (one Braceworks system), hung at z, and get the position name. Use vw_insert_truss_run for a single straight run. All-or-nothing; one revertible step. Returns {system, piece_length, straights, corners, legs: [{pieces, length, gap, turn}], imported, items: [{uuid}], class?}; check with vw_list_truss.

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": {
      "straight": "<straight>",
      "corner": "<corner>",
      "path": "<path>"
    },
    "name": "vw_insert_truss_path"
  }
}

Input Schema

NameRequiredDescriptionDefault
zNoHow high to raise the truss in document units: its underside sits at z, the centre line half the truss height above. Default 0.
fitNoWhere a leg's leftover goes when whole pieces do not fill it: 'start' (default) leaves the gap at the leg's end, 'center' splits it between both ends, 'end' leaves it at the leg's start.start
pathYes[[x, y], ...] in document units: the centre line of the truss, at least two points. Every interior point gets a corner.
layerNoDesign layer to place the new object(s) on, by name. Omitted: the user's active layer.
cornerYesName of the corner symbol of the same truss family, such as 'Global Truss F34C21 Corner' (90 degrees), F34C20 (60), F34C22 (120), F34C23 (135). The path's bends must match the corner's angle.
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.
straightYesName of the straight truss symbol (in the document, or in library_path), such as 'Global Truss F34-300 Straight'. Its Braceworks record gives the piece length.
class_nameNoClass to assign to the new object(s), by name; it must exist (vw_create_class or vw_apply_class_standard first). Applied in a second job after the insert. Omitted: the user's active class.
library_pathNoLibrary .vwx file (vw_list_library) to import the symbols from when they are not in the document yet.
position_nameNoSpotlight position name written on every piece, so fixtures can hang on it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world write; the description adds the important behavioral facts: it is "All-or-nothing; one revertible step," pieces are linked in order into one system, and every leg loses length to the leftover gap per `fit`. It does not cover failure modes of the document guard or the second-pass class assignment, but the mutation profile is well disclosed.

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-loaded with the purpose, then the leg/corner/gap mechanics, then the sibling pointer Society and the return contract. Dense but nearly every sentence carries information; the multi-line wrap is slightly harder to scan than a single lead sentence would be, but nothing is 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 10-parameter mutation tool with no output schema, the description covers input semantics, atomicity/revertibility, the system chaining behavior, and explicitly enumerates the return keys (system, piece_length, straights, corners, legs, imported, items, class). Nothing an agent needs to call or interpret the result is missing.

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?

Schema coverage is 100%, so the baseline is 3; the description goes further by explaining the geometric interaction between `straight`, `corner`, `path` and `fit` — corners consume length from both legs and the leftover gap is distributed per `fit`. That adds real intuition about how parameters interact that the individual field descriptions do not convey.

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?

Opens with a concrete verb and resource plus the accepted shapes: "Build a truss shape (L, U, rectangle, any polyline with matching bends) from straights and corners, one chained system." It also names the distinguishing factor versus the sibling, stating this is one chained Braceworks system rather than a single run, so an agent can route correctly without reading schemas.

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?

Explicitly routes to the alternative: "Use vw_insert_truss_run for a single straight run," and names a verification path, "check with vw_list_truss." It also states a pre-condition for correct use ("The path's bends must match the corner's angle," though that appears in the schema), giving both when-to-use and when-not.

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