Skip to main content
Glama
Sign In
SolidworksMCP-python

SolidworksMCP-python

by andrewbartels1
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

pack_and_go_assembly

Copy a SolidWorks assembly and all its referenced parts into a self-contained folder, rewriting component paths so the assembly opens without dependency on original file locations.

Instructions

Copy a SolidWorks assembly and all its referenced parts to a self-contained folder.

Enumerates every component referenced by the active assembly, copies the assembly and each part into target_dir, then rewrites the stored component paths inside the copied assembly so it opens without any dependency on the original file locations — equivalent to the SolidWorks GUI Pack-and-Go operation.

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": "pack_and_go_assembly"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataNoThe input data value. Defaults to None.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.3/5.0
Behavior4/5

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

Discloses key behavioral traits: enumerates components, copies files, rewrites paths, and eliminates original dependencies. Does not explicitly state that original files are unmodified, but with no annotations, coverage is good.

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?

Concise two-paragraph structure: first sentence states core purpose, second paragraph details mechanics. Front-loaded and no superfluous information.

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?

Given the tool's complexity and presence of an output schema (per context signals), the description sufficiently covers the operation's essentials. No need to detail return values per rules.

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%, so baseline 3 applies. Description does not add significant meaning beyond the schema's parameter descriptions, which already detail source_path, target_dir, export_preview, and overwrite.

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?

Description clearly states 'Copy a SolidWorks assembly and all its referenced parts to a self-contained folder' with specific verb and resource. Distinguishes from sibling tools which are about modeling, sketching, or drawing operations.

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?

Describes the operation as equivalent to SolidWorks Pack-and-Go, implying usage for creating self-contained copies. However, it does not mention when not to use or provide alternatives, though context makes it clear.

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