Skip to main content
Glama
Vectorworks MCP

Vectorworks MCP

vw_list_library

Read-only

Search Vectorworks library files by path keywords or list symbols and resources inside one file to find resources for import and insertion.

Instructions

Browse the Vectorworks libraries: find library files on this Mac by words in their path, or list the symbols inside one file.

Read-only, imports nothing. Without path it searches the application and user library folders on disk (no job; only libraries that are actually downloaded are found, many are download-on-demand) and returns {query, count, files: [{library, folder, name, path}]}. With path Vectorworks reads that file's resource list and returns {path, type_code, count, names}. Typical flow: search, then list one file, then vw_import_resource brings a symbol into the document for vw_insert_symbol or the typed insert tools.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vw_list_library"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute path of one library .vwx file (from a previous call's `files`): list the resources inside it instead of searching files.
limitNoMaximum number of files or resource names to return.
queryNoWithout path: words that must all appear in a library file's path, case-insensitive, such as 'truss', 'lighting', 'people', 'stage deck' or 'audio'. Empty lists every library file.
type_codeNoWith path: Vectorworks resource type, 16 = symbol definitions (includes plug-in styles such as truss, lighting pipe and fixture symbols), 47 = record formats.
name_containsNoWith path: keep only resources whose name contains this text, case-insensitive.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint=false; the description adds real value beyond them by stating it 'imports nothing', spelling out both return shapes ({query,count,files:[...]} and {path,type_code,count,names}), and warning that only locally downloaded libraries are found. It stops short of covering failure behavior for an invalid path or the cost of large resource reads.

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?

Purpose is front-loaded, followed by read-only status, then the two modes, then the typical flow — a sensible order with no wasted sentences. Minor redundancy exists between 'Read-only, imports nothing' and the readOnlyHint annotation.

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?

With no output schema, the description compensates by documenting both response shapes and the download-on-demand limitation. What remains thin is guidance on how many files a search typically returns and what happens if `path` points at a non-library file.

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% and each parameter's description already documents its role, including the 'without path' / 'with path' qualifiers and the type_code values. The description reinforces the mode interaction but adds little syntax or meaning not already present in 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?

The description opens with a specific verb and resource ('Browse the Vectorworks libraries') and immediately disambiguates its two modes: finding library files by path words, or listing symbols inside one file. It also names the downstream sibling (vw_import_resource) that consumes the result, so an agent knows exactly what this tool does versus what follows it.

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

Usage Guidelines4/5

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

It gives explicit mode-selection guidance ('Without `path`... With `path`...') plus a recommended flow of search → list one file → vw_import_resource. It does not, however, distinguish itself from document-scoped siblings such as vw_list_symbols, which an agent could plausibly confuse with listing library symbols.

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