Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Export STL

export_stl
DestructiveIdempotent

Exports the active SolidWorks part or assembly to an STL file for 3D printing; resolves lightweight components and writes to the specified .stl path.

Instructions

Export the active document to STL, like File > Save As with the STL type.

Use it for 3D printing. An assembly is exported whole, with lightweight components resolved first. SolidWorks picks the format from the file's extension, so end file_path in .stl. Needs: an open, active part or assembly. Changes: writes the file, creating its folder and replacing a file already there; the open document is unchanged. Returns: export with file_path and format, plus warning when SolidWorks wrote the file without its STL options (bodies not merged into one file).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe export. `file_path` (ending in .stl) is required; `format_type` is not needed: the file extension decides the format.

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?

Goes well beyond the annotations by disclosing that it writes a file, creates the containing folder, and overwrites an existing file, while leaving the open document unchanged — consistent with destructiveHint=true and idempotentHint=true. It also exposes a non-obvious edge case: assemblies are exported whole with lightweight components resolved, and a `warning` is returned when SolidWorks skipped its STL options.

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 the core action and the UI analogy, then organized into Needs/Changes/Returns blocks that are easy to scan. Dense but nearly every line carries information an agent would otherwise have to guess.

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?

Covers preconditions, side effects on disk, what stays untouched, and the partial-success warning signal, which is the failure mode most likely to be missed. Despite an output schema existing, the return description adds the conditional `warning` semantics that an agent needs to interpret results correctly.

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, but the description adds operational meaning: `file_path` must end in .stl and `format_type` is unnecessary because the extension picks the format. That is genuinely useful for avoiding a wrong-format export, though it largely restates what the schema already documents.

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 ("Export the active document to STL") and anchors it to a familiar UI equivalent ("like File > Save As with the STL type"). The STL format name alone separates it from export_step, export_iges, and export_dwg siblings.

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 case ("Use it for 3D printing") and a precondition ("an open, active part or assembly"). It does not explicitly route the agent to a different export_* tool when another format is wanted, but the extension-decides-format rule makes the choice fairly self-evident.

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