Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Load Part

load_part
Idempotent

Opens a .sldprt part file from disk and makes it the active document so you can start work on an existing part. Deprecated: use open_model instead.

Instructions

Deprecated: use open_model.

Open a part (.sldprt) from disk and make it the active document.

Use it to start work on an existing part; 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 .sldprt is refused. Needs: the file on disk. Changes: opens the part (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_part"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYesThe part. `file_path` (a .sldprt) is required.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false; the description complements this by stating 'no file is written' and that non-.sldprt paths are refused, removing ambiguity around the mutation. It further explains that `configuration` may be null when unreadable, which is real behavioral context; the deprecation notice adds lifecycle awareness. It stops short of noting any side effects on an already-open document or error behavior beyond the refusal.

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 deprecation warning, then purpose, alternatives, constraints, and a compact Needs/Changes/Returns block. Every sentence carries distinct information and the structured summary makes scanning fast.

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 single-parameter open operation with an output schema already present, the description covers lifecycle (deprecated), prerequisites (file on disk), mutation scope (no file written), validation (non-.sldprt refused), and routing to the preferred alternative. Nothing an agent needs to call it correctly is missing.

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% with a single required `file_path`, so the schema already carries the parameter documentation, making 3 the baseline. The description's only added constraint is that a non-.sldprt path is refused, which mildly reinforces the file-type expectation but adds little beyond the schema's own 'Full path to the .sldprt file'.

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 (.sldprt) from disk') and its session effect ('make it the active document'), plus a deprecation banner pointing to the replacement. It is clearly distinguishable from open_model (any type) and activate_document (already-open docs).

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 names when to use it ('to start work on an existing part') and two alternatives with their selecting conditions: open_model for any document type and activate_document for already-open documents. The refusal condition for non-.sldprt paths is also given.

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