Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_switch_document

Switch the active Vectorworks document by bringing a named open, saved file to the front so subsequent edits and exports target the correct drawing.

Instructions

Bring one of the open, saved Vectorworks documents to the front.

Changes only which document is active (no drawing change); verified afterwards by reading the front window's name. All other tools act on the active document, so use this before writing when vw_list_documents shows the wrong one in front. Returns {active, switched, documents}.

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

Input Schema

NameRequiredDescriptionDefault
nameYesThe document to bring to the front: its name as vw_list_documents shows it (".vwx" may be left out) or its full path. It must already be open and saved; unsaved documents cannot be switched to and closed files are not opened.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.1
    • addedInput schema / properties / name / description
      Added value: +"The document to bring to the front: its name as vw_list_documents shows it (\".vwx\" may be left out) or its full path. It must already be open and saved; unsaved documents cannot be switched to and closed files are not opened."
  2. Added

TDQS

A4.7/5.0
Behavior5/5

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

Beyond the supplied annotations, which mark it non-destructive but not read-only, the description discloses that only the active window changes with no drawing modification, that the result is verified by reading the front window's name, and that unsaved or closed documents cannot be targeted. That is exactly the behavioral context an agent needs for a state-changing switch.

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-loads the action, then the effect, then the verification, then the routing rule, then the return shape. Every sentence carries information that an agent needs, and there is no 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?

There is no output schema, but the description spells out the return object {active, switched, documents} and covers the preconditions and side effects. Nothing needed to call this correctly 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%, and the schema description already explains the name formats and the open/saved requirement. The prose reiterates this constraint but adds no additional syntax or format detail beyond the schema, so the baseline of 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: bring an open, saved Vectorworks document to the front. It also distinguishes itself from vw_list_documents, which the agent should consult first, so the agent can identify scope without reading 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?

Explicitly says when to use it (before writing, when vw_list_documents shows the wrong document in front) and explains why: all other tools act on the active document. It also names the prerequisite condition of using a saved, already-open document, leaving no inference needed.

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