Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Export STEP

export_step
DestructiveIdempotent

Export the active SolidWorks part or assembly to STEP (.step/.stp) for sharing models with other CAD systems. Supply a full path; existing files are replaced and the open document is unchanged.

Instructions

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

Use it to hand a model to another CAD system; it is the most widely read exchange format. SolidWorks picks the format from the file's extension, so end file_path in .step or .stp. 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.

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_step"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe export. `file_path` (ending in .step or .stp) 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.7/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: it states the prerequisite (open, active part or assembly), the side effects (writes the file, creates the folder, replaces an existing file), and the guarantee that the open document is unchanged. This corroborates destructiveHint=true and idempotentHint=true rather than contradicting them, telling the agent exactly what gets overwritten.

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?

Front-loaded with the action, then explicitly labeled 'Needs:', 'Changes:' and 'Returns:' blocks that an agent can scan in one pass. The Save As analogy and the extension rule are load-bearing rather than filler.

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 prerequisites, write/overwrite behavior, format selection, and the return payload on a nested-parameter tool with an output schema. Nothing an agent needs in order to call this safely 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 goes further by naming the acceptable extensions (.step or .stp) and explaining that the extension — not format_type — selects the format. That adds a constraint the file_path schema entry does not spell out.

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 STEP' — and the File > Save As analogy pins down the exact semantics. The format-specific framing distinguishes it from sibling exporters like export_iges and export_stl without needing to name them.

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 a clear when-to-use rule: hand a model to another CAD system, with the rationale that STEP is the most widely read exchange format. That implicitly argues for STEP over the other format exporters, but it never explicitly excludes or routes to a named alternative, so it falls short of a 5.

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