Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Open Model

open_model
Idempotent

Opens an existing SolidWorks part, assembly, or drawing from disk and sets it as the active document so you can begin editing or reviewing it.

Instructions

Open a part, assembly or drawing from disk and make it the active document.

Use it to start work on an existing file. To switch to a document that is already open, use activate_document. Needs: the file on disk (a vault file must be checked out). Changes: opens the document; nothing is written. Returns: model with title, type, path and configuration.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe file. `file_path` (.sldprt, .sldasm or .slddrw) is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

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?

Adds prerequisites and side effects beyond the annotations: the file must exist on disk, a vault file must be checked out, and 'nothing is written' despite readOnlyHint=false (the tool changes application state, not disk). The stated return fields are extra value even though an output schema exists. It stops short of describing failure modes (missing file, failed checkout) or how configuration is chosen.

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?

Front-loaded with the verb and effect, then organized into short labeled clauses (Needs/Changes/Returns) with no filler. Every sentence adds information an agent would otherwise have to infer.

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?

Covers purpose, prerequisite, side effect, and return shape for a simple one-parameter tool, and an output schema is present so return details needn't be expanded. The remaining gap is error behavior — what happens if the file is absent or the vault check-out fails.

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 coverage is 100% and the only parameter is a fully documented `file_path` with allowed extensions, so the schema carries the weight. The description adds the vault-checkout constraint, which is meaningful but is a precondition rather than extra semantics for the parameter itself. Baseline 3 is appropriate.

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 a part, assembly or drawing from disk') plus the resulting effect ('make it the active document'). It explicitly contrasts with the sibling `activate_document`, so an agent can distinguish the two without opening either schema.

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?

Gives an explicit when-to-use ('Use it to start work on an existing file') and a when-not/'alternative' rule ('To switch to a document that is already open, use `activate_document`'). The routing decision is fully determined by the file's open state.

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