Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Pack and Go Assembly

pack_and_go_assembly
DestructiveIdempotent

Copy an assembly and its referenced files into one folder that opens standalone for handover or archiving; warns about unsaved changes and can add a preview.

Instructions

Copy an assembly and every file it uses into one folder that opens on its own.

Use it to hand over or archive an assembly. SolidWorks lists the files the assembly uses; each is copied under its own name, as saved on disk, so save first: a warning names any open file whose unsaved changes the copy doesn't have. The copy opens with its own parts, since SolidWorks looks in the assembly's folder first. It fails, copying nothing, when a file is missing, two files share a name, or target_dir holds the originals. It refuses a folder that already has files unless overwrite is on, and then replaces only the files it copies. It never closes or changes a document. It can add an isometric PNG preview. Needs: the .sldasm on disk. Changes: writes the copies into target_dir, creating it if needed. Returns: source_assembly, target_dir, copied_files, source_files, unsaved_changes and, with a preview, preview_image.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe copy. `source_path` (a .sldasm) and `target_dir` are required; `export_preview` and `overwrite` are off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only say readOnly=false, destructive=true, idempotent=true; the description goes far beyond by enumerating failure modes (missing file, duplicate names, target_dir containing the originals), the non-empty-folder refusal and overwrite scoping ('replaces only the files it copies'), and the guarantee that no document is closed or modified. The unsaved-changes warning behavior is exactly the kind of mutation risk an agent needs before calling.

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?

Purpose is front-loaded in the first sentence, then usage, then failure modes, then a compact Needs/Changes/Returns block. Sentences are dense with new facts; nothing is filler.

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 destructive, nested-parameter copy operation, the description covers prerequisites, mutation surface, failure modes, and side effects thoroughly. The trailing 'Returns:' field list partly duplicates the existing output schema, so it adds length without adding information, which is the only notable slack.

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 baseline is 3; the description adds real meaning on top — overwrite only replaces the files Pack and Go writes and keeps other files, target_dir must not hold the originals, and export_preview yields an isometric PNG. These are usage consequences rather than restatements of the schema text.

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 — copy an assembly plus every file it uses into a self-contained folder — which is immediately distinguishable from save_assembly or create_assembly. The self-containment outcome ('opens on its own') conveys the defining property of Pack and Go rather than restating the title.

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?

Gives an explicit use context: 'Use it to hand over or archive an assembly,' plus a precondition ('save first') and a set of abort conditions. It does not name a sibling alternative (e.g., when to prefer save_assembly), so the when-not guidance is behavioral rather than comparative.

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

Deploy Server

Other Tools