Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

close_document

Closes the active document, with an optional save-first step. Use save=false to close unsaved documents or save new files before closing with save=true.

Instructions

Close the current document. save = true saves it first, but a document that was never saved is refused then (save_document first, or close with save = false).

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

Input Schema

NameRequiredDescriptionDefault
saveNoSave the document first

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.4/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 burden, and it discloses the key non-obvious behavior: save = true attempts a save first, and a never-saved document is refused in that mode. This is exactly the kind of edge case an agent would otherwise hit blind. It does not explicitly say that save = false discards unsaved modifications, though that is implied.

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?

Two tight sentences with the core action front-loaded and the conditional caveat immediately after. There is no redundancy and every clause carries information an agent needs before calling.

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 single-boolean tool with no output schema, the description covers the operation, the flag's effect, and the one failure mode worth knowing. The only residual gap is an explicit statement that closing without saving discards pending changes, which would make it fully self-contained.

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 the baseline is 3, but the description adds real meaning beyond the schema's terse 'Save the document first': it explains the interaction between save and the never-saved-document refusal, plus the two valid ways to handle that case. That is value the schema alone does not convey.

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 opening sentence pairs a specific verb with a specific resource ('Close the current document'), making the operation unambiguous and easily separable from siblings like save_document, open_document, or close_sketch. The follow-up clause reinforces the distinction by naming save_document as the alternative for the save path.

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 conditional guidance: for an unsaved document, either call save_document first or close with save = false. That is a clear routing rule for the main branch point. It stops short of stating when not to use it (e.g., closing a document that is still being edited elsewhere), so it is strong but not exhaustive.

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