Skip to main content
Glama
Sign In
SolidWorks-MCP

SolidWorks-MCP

by hjbaard
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

open_assembly

Opens .sldasm files or imports STEP/IGES/Parasolid assemblies as the current document, positioning parts as components ready for component listing and mating; single-part files are rejected.

Instructions

Open a .sldasm, or import a STEP/IGES/Parasolid assembly; it becomes the current document.

An imported assembly's parts arrive as components at their places, ready for list_components and add_mate; the result gives the component count. A file holding a single part is refused (use open_part), and an import over 30 MB unless allow_large=True (it can outlast the 2-minute call limit).

Input Schema

NameRequiredDescriptionDefault
pathYes
allow_largeNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.17.0
    • addedInput schema / properties / allow_large
      Added value: +{
+  "default": false,
+  "title": "Allow Large",
+  "type": "boolean"
+}
  2. First observedv0.4.0

TDQS

A4.9/5.0
Behavior5/5

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

With zero annotations the description carries the full burden and does so: it discloses what the import produces (components at their original places), the refusal behaviors (single part, >30 MB), and the operational risk that large imports can exceed the 2-minute call limit. That timeout warning is exactly the kind of hazard an agent cannot infer from the schema.

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 action, then consequences, then exceptions. Every clause carries information — no restatement of the name or filler phrasing.

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?

No output schema exists, but the description still tells the agent the result reports the component count. Combined with the refusal conditions and the size/timeout caveat, an agent has everything needed to call it correctly.

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 0%, so the description must compensate. It defines allow_large's threshold behavior (over 30 MB) and constrains path to the accepted formats (.sldasm, STEP, IGES, Parasolid). Path format specifics (absolute vs relative, extension requirements) remain unstated.

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 (open/import) and resource (.sldasm and STEP/IGES/Parasolid assemblies) and the side effect that it becomes the current document. It explicitly names the sibling it is not (open_part) and the condition that distinguishes them, so no schema inspection is needed to choose.

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?

Explicit exclusions and alternatives: single-part files are refused, route to open_part; imports over 30 MB require allow_large=True. It also names its follow-on tools (list_components, add_mate) giving the agent clear workflow context.

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