Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_export_stl

Exports the active SOLIDWORKS part as an STL file to a chosen path, clearing any face selection first so the full model is written instead of only selected faces.

Instructions

导出 STL(默认 /agent_part.STL)。导出前清空选择,避免只导出选中面。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "sw_export_stl"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does add real value by revealing a side effect: the selection is cleared before export so that only whole-part geometry is written, not selected faces. It remains silent on overwrite behavior, what happens if no part is open, and what the call returns, which are meaningful gaps for a file-writing operation.

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?

Two short sentences with no filler, and the export action plus default path are front-loaded before the selection-clearing caveat. The parenthetical default path is well placed. Minor deduction because the '<out>' token is left unexplained and reads as an opaque internal reference.

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?

For a one-optional-parameter export tool with no output schema, the description covers the essentials: what is produced, where it defaults to, and the geometry-selection side effect. Missing details about overwriting and error conditions keep it from being fully complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% for the single optional `path` parameter, so the description has to compensate. It partially does by stating the default output location (<out>/agent_part.STL), which explains what an empty path means. However, the '<out>' placeholder is undefined, and nothing is said about accepted path formats or directory-creation behavior.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/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 STL. That distinguishes it from the save_part category of siblings well enough for an agent to recognize it as a mesh export tool. It does not explicitly contrast with sw_save_part or sw_open_in_bambu, so it stops short of full sibling differentiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied rather than stated: an agent can infer this is the step for producing an STL for downstream printing or slicing, but the description never says when to prefer this over saving or opening in Bambu. The only guidance offered is an internal defensive behavior (clearing selection), not a condition for choosing this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.