Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Close Model

close_model
Destructive

Closes the active SolidWorks document, optionally saving it first when save is enabled; unsaved changes are lost otherwise.

Instructions

Close the active document, saving it first only if asked.

Use it when you are done with a document. Unsaved changes are lost unless save is on. Needs: an open, active document. Changes: closes the document, and with save writes it first. Returns: saved, whether a save was asked for.

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": {
      "input_data": "<input_data>"
    },
    "name": "close_model"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe close. Nothing is required: `save` is off.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already flag destructiveHint=true, but the description goes further by naming the actual consequence: unsaved changes are lost unless `save` is on, with save defaulting off. It also discloses the precondition of an active document and the effective outcome ('with save writes it first'), which is precisely the context an agent needs before a destructive call.

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 Needs/Changes/Returns labeling is front-loaded and scannable, and the data-loss warning sits right next to the operation. The one weak line is the explicit return-value statement, which duplicates the output schema and could be dropped.

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

Completeness5/5

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

For a destructive, single-parameter tool with a nested input object, the definition covers the precondition, the destructive consequence, the parameter effect, and the outcome. Nothing an agent needs in order to call it safely is missing.

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% and the `save` property already documents 'Save the model before closing' with default false, so the baseline is 3. The description adds meaning the schema lacks — that omitting `save` means data loss, not just a no-op — which is a genuine semantic addition for the single parameter.

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 opens with a specific verb+resource ('Close the active document') and immediately qualifies the behavior ('saving it first only if asked'), which makes the operation unambiguous. It doesn't name a sibling such as open_model, but the close/open distinction is inherent in the verb and the 'active document' scoping.

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 explicit when-to-use guidance ('Use it when you are done with a document') and a hard prerequisite ('Needs: an open, active document'). It stops short of stating when not to use it or naming an alternative for cases where the document should stay open, so it is clear context rather than full routing 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