Skip to main content
Glama
solidworks-mcp

solidworks-mcp

sw_save_part

Saves a SOLIDWORKS part (.SLDPRT) to disk at a specified path, using /agent_part.SLDPRT by default to persist the modeled CAD file.

Instructions

保存 .SLDPRT 到磁盘(默认 /agent_part.SLDPRT)。

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

Input Schema

NameRequiredDescriptionDefault
pathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It discloses the default path (<out>/agent_part.SLDPRT), which is useful, but says nothing about overwrite behavior, whether it saves the current in-memory model state, or error conditions.

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?

A single sentence that front-loads the action and the default, with no wasted wording.

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

Completeness3/5

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

For a one-optional-parameter save tool with no output schema, the description covers the essentials of what happens by default, but leaves the agent unsure about overwrite semantics and the return value.

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 description coverage is 0% and the single 'path' parameter is only titled 'Path' with an empty default. The description partially compensates by explaining the default destination, but does not clarify path format, whether <out> is resolved server-side, or what an empty value means.

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?

States a concrete verb+resource: saves an .SLDPRT file to disk. The file format makes it distinguishable from sw_export_stl, but it does not explicitly contrast with that sibling.

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

Usage Guidelines2/5

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

No guidance on when to call this versus sw_export_stl or other output tools; usage is only implied by the description of saving the part file.

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