Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Export IGES

export_iges
DestructiveIdempotent

Exports the active SolidWorks document to IGES for receivers that cannot read STEP; provide a .igs or .iges file path.

Instructions

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

Use it only when the receiver can't read STEP; prefer export_step. SolidWorks picks the format from the file's extension, so end file_path in .igs or .iges. 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_iges"
  }
}

Input Schema

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

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds substance beyond them by spelling out what is actually affected: it creates the target folder, replaces a file already there, and leaves the open document unchanged. It also names the return payload (`export` with `file_path` and `format`), which is more than the annotations convey.

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 purpose, then a labeled Needs/Changes/Returns block that makes scanning trivial. Every sentence carries distinct information; the Save-As analogy replaces several lines of explanation.

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 single-parameter export with an output schema already present, the description still covers preconditions, side effects, overwrite behavior, and the sibling alternative. Nothing an agent needs in order to call it correctly is missing, and the return-value note is redundant but harmless.

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 baseline would be 3, but the description adds the causal rule the schema only asserts: SolidWorks derives the format from the file extension, so `file_path` must end in .igs/.iges and `format_type` is unnecessary. That explains why the optional parameter exists rather than merely restating its default.

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 IGES') and immediately anchors it with an analogy ('like File > Save As with the IGES type'). It also names the sibling it is not ('prefer `export_step`'), so an agent can distinguish it from the other export_* tools without opening a 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 when-to-use rule ('Use it only when the receiver can't read STEP') plus a named preferred alternative (`export_step`) for the default case. It also states the calling precondition ('Needs: an open, active part or assembly'), leaving nothing critical to inference.

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