Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

export_stl

Export the active SOLIDWORKS part or assembly to an STL file for 3D printing or meshing, setting resolution, file unit and binary or ASCII format without altering the document.

Instructions

Export the active part or assembly as an STL file (.stl) for 3D printing or meshing: one file, in the model's own coordinates. resolution: fine (the default), coarse, or custom with deviation and angle. file_unit is the unit the file's numbers are in (STL files carry none): the document's length unit by default, or mm if that is not mm, cm, m, inch or ft. The document is not saved, renamed or changed, and SolidWorks' STL settings are put back afterwards. Reports the triangles and the file's bounding box in mm next to the model's. An STL file carries no unit: tell the user the file_unit the result names.

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": {
      "filepath": "<filepath>"
    },
    "name": "export_stl"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNoUnit of deviation: mm, cm, m, inch or ft (default: the session unit, mm unless set_units changed it)
angleNoWith resolution custom: the largest angle between neighbouring triangles, degrees (0-90]
formatNoFile formatbinary
filepathYesWhere to write it, e.g. C:\Work\bracket.stl
deviationNoWith resolution custom: the largest gap between the triangles and the true surface (in unit)
file_unitNoUnit of the numbers in the file (default the document's length unit)
resolutionNoHow finely curved faces are cut into trianglesfine

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full behavioral burden and discloses important side effects: the document is not saved, renamed, or changed, and SolidWorks STL settings are restored afterwards. It also explains unit behavior and reported outputs, though it omits overwrite/error behavior when writing the filepath.

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 description is dense but front-loaded with the export purpose and key constraints. It is appropriately sized for a seven-parameter export tool, though the final sentence repeats the earlier point that STL files carry no unit.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given seven parameters, no annotations, and no output schema, the description is substantially complete: it covers side effects, units, resolution behavior, and the reported result. The main remaining gap is file-writing behavior such as overwrite handling or path errors.

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 already 100%, so the schema documents all seven parameters. The description still adds useful semantics by linking custom resolution to deviation and angle, explaining file-unit fallback behavior, and warning that STL files carry no intrinsic unit.

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 states a specific verb and resource: export the active part or assembly as an STL file. It adds the scope (one file, model coordinates) and intended use (3D printing or meshing), so an agent can distinguish it from other export tools without opening the schema.

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?

It gives clear context for use, namely 3D printing or meshing, which implies the right choice among export formats. It does not explicitly name alternatives such as export_step or state when not to use this tool, so it falls short of full when/when-not guidance.

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