Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_delete_objects

Permanently deletes objects by UUID in an open Vectorworks drawing. Bulk deletion is all-or-nothing: if any UUID is unknown, nothing is removed and the call fails.

Instructions

Permanently delete objects by UUID; the one write that vw_revert_last cannot undo. Only Cmd-Z inside Vectorworks can bring them back, and the deletion also blocks reverting earlier journaled edits, so confirm with the user before calling it. To undo something a tool placed, use vw_revert_last instead of deleting by hand. All-or-nothing: if any UUID is unknown nothing is deleted. Returns {deleted: 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_delete_objects"
  }
}

Input Schema

NameRequiredDescriptionDefault
uuidsYesUUIDs of the objects to delete, from vw_find_objects, vw_get_selection or a tool result. At least one; one unknown UUID deletes 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. Changed2 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 / uuids / description
      Added value: +"UUIDs of the objects to delete, from vw_find_objects, vw_get_selection or a tool result. At least one; one unknown UUID deletes nothing."
  2. Added

TDQS

A3.9/5.0
Behavior1/5

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

The description declares a permanent, irreversible deletion that also blocks reverting earlier journaled edits, while the annotations declare destructiveHint=false, which per MCP semantics means only additive, non-destructive updates. The two cannot both be true; the description is the accurate side and the annotation is the outlier, but the conflict is exactly what an agent cannot resolve on its own.

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?

Front-loaded with the single most decision-relevant fact (permanent, unrecoverable), then the alternative, then the atomicity rule, then the return shape. No filler sentences; each one changes how an agent would act.

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 two-parameter write tool with no output schema, the description supplies the return shape ({deleted: n}), the failure mode (unknown UUID deletes everything or nothing), the recovery path (Cmd-Z only, inside Vectorworks), and the human-confirmation requirement. Nothing an agent needs before calling 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 description coverage is 100%, so both parameters are already fully documented, including provenance (vw_find_objects, vw_get_selection) and the document-precondition rule. The description adds the all-or-nothing atomicity framing, but that is already stated in the uuids parameter description, so the marginal value is limited.

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?

"Permanently delete objects by UUID" states a specific verb, resource, and identity key in five words, and the description immediately distinguishes this tool from vw_revert_last. An agent can tell what it does and what it is not without opening the 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?

Explicit when-to-use-vs-alternative routing: "To undo something a tool placed, use vw_revert_last instead of deleting by hand," and an explicit gate, "confirm with the user before calling it." Exclusions and preconditions are both named, not implied.

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