Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Save Part

save_part
DestructiveIdempotent

Saves the active SolidWorks part in place or to a new .sldprt path, checking the target folder and refusing existing files unless overwrite is enabled.

Instructions

Deprecated: use save_file.

Save the active part in place, or as a new .sldprt with the target path checked first.

Before writing to a new path it checks the folder exists and is writable, changes the extension to .sldprt, and refuses an existing file unless overwrite is on. For other formats, use save_as or an export_* tool. Needs: an open, active part. Changes: writes the part file. Returns: file_path when saved to a new path.

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

Input Schema

NameRequiredDescriptionDefault
input_dataNoThe save. Nothing is required: give `file_path` for a new path or omit it to save in place; `overwrite` is 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?

Beyond the annotations, it discloses the folder-existence and writability checks, automatic extension change to .sldprt, refusal of existing files unless overwrite is enabled, and the returned file_path for new-path saves. These details materially explain the write behavior and the destructiveHint=true annotation is consistent with saving over a file when overwrite is on.

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?

The deprecation warning is front-loaded, followed by the save behavior, checks, alternatives, prerequisites, effects, and return value in a compact sequence. It is slightly dense but each clause carries useful operational 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?

For a deprecated single-parameter save tool with an output schema and rich annotations, the description covers prerequisites, side effects, refusal conditions, alternatives, and return behavior. An agent has enough information to decide not to use it or to invoke it correctly if required.

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 already documents file_path and overwrite defaults. The description reinforces that omitting file_path saves in place and overwrite controls existing-file refusal, but it adds little parameter meaning beyond the schema itself.

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 by declaring the tool deprecated and then states exactly what it does: save the active part in place or as a new .sldprt. It also distinguishes the tool from siblings by naming save_file, save_as, and export_* for alternatives.

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?

It explicitly says to use save_file instead because the tool is deprecated, and it names save_as or export_* for other formats. It also states the prerequisite of an open, active part, leaving little ambiguity about when to call it.

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