Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Load Assembly

load_assembly
Idempotent

Open an existing SolidWorks assembly (.sldasm) from disk and make it the active document to start assembly work.

Instructions

Deprecated: use open_model.

Open an assembly (.sldasm) from disk and make it the active document.

Use it to start work on an existing assembly; for any document type, use open_model, and to switch to a document that is already open, use activate_document. A path that isn't a .sldasm is refused. Needs: the file on disk. Changes: opens the assembly (no file is written). Returns: model with name, type, path and configuration (the one SolidWorks opened, or null when it can't be read).

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe assembly. `file_path` (a .sldasm) is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior4/5

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

Goes beyond the annotations by disclosing preconditions ('the file on disk'), the scope of the mutation ('opens the assembly (no file is written)' — reconciling the readOnlyHint=false with a no-write operation), and the refusal of non-.sldasm paths. What remains unstated is failure behavior for a missing/locked file or whether a previously active document is closed.

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?

Front-loaded with the deprecation notice and the core action, then a labeled Needs/Changes/Returns contract that is easy to scan. `open_model` is referenced twice (deprecation line and usage line), a minor redundancy, but no sentence is filler.

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?

Complete for a one-parameter tool: preconditions, alternatives, refusal rule, and a non-obvious return field (`configuration`, nullable) are all covered. The return detail is somewhat redundant with the output schema, but it costs little and removes ambiguity about the nested shape.

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 nested `input_data.file_path` shape is already fully documented and the baseline is 3. The description adds acceptance semantics beyond the schema by declaring that a non-.sldasm path is refused, which tells the agent how the parameter is validated.

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?

States a specific verb and resource ('Open an assembly (.sldasm) from disk and make it the active document') with the file type and the side effect on active-document state. It also opens with a deprecation pointer to `open_model`, so an agent knows both what it does and that a preferred sibling exists.

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

Usage Guidelines5/5

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

Explicitly routes between three cases: use this to start work on an existing assembly, use `open_model` for any document type, and use `activate_document` for something already open. It also states the refusal condition (a path that isn't a .sldasm), which is a concrete when-not rule.

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