Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

save_document

Saves the current SOLIDWORKS document in place or to a given path; file extensions export copies, and existing files or unsaved referenced files require explicit overwrite or save approval.

Instructions

Save the current document. With filepath it is saved under that name and the extension chooses the format: .SLDPRT / .SLDASM / .SLDDRW keep the document, while .pdf, .step, .stl, .dxf and the like export a copy; without filepath it saves in place. Saving a drawing or assembly that has open referenced files with unsaved changes is refused (naming them) unless save_referenced is true, and a Save As onto an existing file (other than the document's own) is refused unless overwrite is true. A refusal saves nothing.

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": "save_document"
  }
}

Input Schema

NameRequiredDescriptionDefault
filepathNoFull path to save under; leave out to save in place
overwriteNoSave As: replace a file that already exists at filepath
save_referencedNoDrawing or assembly: also write the referenced files that have unsaved changes (they are listed in the result)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full load and does so well: it discloses that certain saves are refused, that refusals name the blocking files, that a refusal saves nothing, and that referenced-file lists appear in the result. These are exactly the failure modes and side effects an agent needs before calling a mutation tool.

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?

It is a single dense paragraph with the core action front-loaded and the conditional rules following in a logical order (format semantics, then refusal conditions, then the refusal guarantee). The sentences are long and multi-clause, which slightly hurts scannability, but no clause is filler.

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 three-optional-parameter mutation tool with no annotations and no output schema, the description covers modes, format effects, refusal conditions, and escape-hatch flags. The only gap is the success-side behavior: it says referenced files are listed in the result but not what a normal return looks like, which is minor given no output schema exists.

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 a 3 would be the baseline, but the description adds real meaning beyond the schema: it explains that the extension selects the format and that extension choice determines whether the document is kept or a copy is exported, and it scopes overwrite to Save As onto a foreign existing file. That causal explanation is absent from the per-parameter descriptions.

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 opens with a specific verb and resource ('Save the current document') and then immediately distinguishes two operating modes: save-with-filepath (which splits further into keep-document vs export-copy based on extension) and in-place save. That is enough for an agent to separate this from close_document or get_document_info 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 Guidelines4/5

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

The description gives clear conditions for choosing behavior: omit filepath to save in place, supply one to Save As or export, set save_referenced when referenced files are dirty, set overwrite to replace an existing target. It does not name sibling tools or tell the agent when to prefer this tool over, say, an export tool, but the internal when/when-not guidance is explicit and unambiguous.

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