Skip to main content
Glama
SolidWorks MCP Python

SolidWorks MCP Python

by locense

Set Exploded View

set_exploded_view
Idempotent

Switch an open assembly between its exploded and collapsed views. Toggles what the view shows without changing the model, failing as not_found if no exploded view exists.

Instructions

Show the active assembly exploded, or collapse it.

Use it to switch between the exploded view create_exploded_view made and the assembled one. Needs: an open assembly with an exploded view. Changes: what the view shows; nothing in the model. Returns: exploded_view with the view, exploded as read back and the bounding box size_mm. No exploded view 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": "set_exploded_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
input_dataYes`exploded` (true or false).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Adds real disclosure beyond the annotations: the change is limited to what the view shows and nothing in the model, and the response is read back from state (`exploded`, `view`, `size_mm`). The `not_found` error path is also given. With `readOnlyHint=false` and `idempotentHint=true` already supplied, this is well above the bar.

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 imperative sentence, then the Needs/Changes/Returns triad with zero filler. Every clause (prerequisite, side-effect scope, return shape, error) earns its place.

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 toggle, the description covers the prerequisite, the exact state effect, the failure case, and (redundantly but harmlessly) the return values, while annotations cover safety and idempotency. Nothing needed to invoke 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% and the single `exploded` flag is documented in both schema and description ("true shows it exploded, false collapsed"); the description adds no meaning beyond that duplication, so the baseline 3 applies.

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 ("Show the active assembly exploded, or collapse it") and names the creating sibling `create_exploded_view`, which is exactly the distinction an agent needs to pick this toggle over the creator.

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 frames the use case as switching between the exploded view made by `create_exploded_view` and the assembled one, and states the precondition (open assembly with an exploded view) plus the failure mode (`not_found`). It lacks an explicit statement of when NOT to use it, but the routing context is unambiguous.

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