Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Save As

save_as
DestructiveIdempotent

Saves the active SolidWorks document under a new path as a native file or exchange format such as STEP or IGES.

Instructions

Save the active document under a new path, as a SolidWorks file or in an exchange format such as STEP or IGES.

For a SolidWorks format (solidworks, sldprt, sldasm, slddrw) it saves a copy like File > Save As; any other format_type is passed to the exporter. For one known format with its options, prefer export_step, export_stl and the other export_* tools. Needs: an open, active document. Changes: writes the file. A file already at file_path is kept and the call refused, unless overwrite is on. Returns: file_path and format.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe target. `file_path` is required; `format_type` defaults to "solidworks", and `overwrite` is off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true and idempotentHint=true, but the description adds the concrete semantics behind them: the call writes a file, an existing file at file_path is preserved and the call refused unless overwrite is on, and a document must be active. Those are exactly the operational details an agent needs before a mutating save.

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?

Front-loaded with purpose, then behavior, then alternatives, using compact labeled fragments (Needs/Changes/Returns) that scan well. The Returns line partially duplicates the existing output schema, which is mild waste but not harmful.

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 nested-parameter mutation tool with an output schema, it covers everything that schema cannot: precondition, side effects, refusal-on-existing-file behavior, and when to prefer a sibling export tool. Nothing an agent needs to call it correctly is missing.

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 the baseline is 3, and the description earns above that by explaining that format_type changes code path (native copy vs exporter) rather than just naming a format. It does not add anything about path conventions or valid format string spellings beyond the schema's example list, which keeps it from a 5.

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 ('Save the active document under a new path') and immediately scopes the two modes: native SolidWorks formats versus exchange formats like STEP/IGES. It also names the sibling family it is not ('prefer export_step, export_stl and the other export_* tools'), so an agent can separate it from the export tools without reading either 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?

Gives an explicit routing rule: native formats behave like File > Save As, any other format_type goes to the exporter, and for a single known format with options the dedicated export_* tool is preferred. It also states the precondition ('an open, active document') that must hold before calling.

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