Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Create Exploded View

create_exploded_view

Explode an active assembly automatically or with step-by-step component moves to visualize assembly structure and prepare an exploded drawing view.

Instructions

Explode the active assembly, automatically or step by step, and show it.

Use it to show how an assembly goes together, and before an exploded drawing view (create_drawing_view with exploded, drawing toolset). With no steps SolidWorks explodes it automatically; each step moves named components a distance along x, y or z. Needs: an open assembly. Changes: adds an exploded view to the active configuration and shows it. Returns: exploded_view with its view name, steps, and the bounding box size_before_mm and size_after_mm. A component it doesn't hold fails as not_found.

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

Input Schema

NameRequiredDescriptionDefault
input_dataYes`steps` (each `components`, `direction`, `distance`, `reverse`); empty explodes it automatically.

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only give readOnly=false / destructive=false / idempotent=false; the description goes well beyond by stating prerequisites ('Needs: an open assembly'), mutation effects ('adds an exploded view to the active configuration and shows it'), return contents, and a concrete failure mode (`not_found`). This is exactly the behavioral context annotations cannot carry.

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 action, then usage, mechanics, prerequisites, side effects, and return shape in a compact Needs/Changes/Returns format. Slightly dense with minor overlap against the schema's own parameter descriptions, but no filler sentences.

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, nested-object tool with an output schema, the description covers prerequisites, mode selection, mutation effects, error behavior, and return fields. 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.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the single nested `steps` structure is already documented, so the baseline is 3. The description adds real meaning on top: empty `steps` triggers automatic explosion, and each step moves named components a distance along x/y/z, clarifying the semantic effect of the parameter rather than restating its type.

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 ('Explode the active assembly') plus the two operating modes (automatic vs. step by step) and the side effect of showing it. The agent can distinguish this from drawing-view creation siblings without opening the schema.

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?

Explicitly says when to reach for it ('to show how an assembly goes together, and before an exploded drawing view') and names the alternative/sequence with `create_drawing_view` + `exploded`. It does not rule out or contrast with the sibling `set_exploded_view`, but the positive guidance is clear.

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