Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

show_exploded

Toggle an assembly's exploded view on or off. Specify the view name when several exist; returns the resulting state and which components moved.

Instructions

Show the active assembly's exploded view exploded (exploded true) or collapsed (false). name picks the view when the configuration has several (default: its only one). Returns the state read back and which components moved.

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": {
      "exploded": "<exploded>"
    },
    "name": "show_exploded"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoExploded view name, e.g. ExplView1 (default: the only one)
explodedYestrue = exploded, false = collapsed

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full disclosure burden. It usefully states the return contract – the state read back plus which components moved – which fills the gap left by the absent output schema, but it says nothing about side effects on the model, whether the state persists with the document, or failure modes.

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?

Three short sentences, front-loaded with the action and followed by the parameter default and return behavior; nothing extraneous. Slight awkwardness in 'exploded view exploded' keeps it from being ideal.

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?

For a two-parameter, non-destructive view-state toggle with no output schema, the description covers action, parameter default, and return values. Missing only persistence and failure-mode details.

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%, so both parameters are already documented in structured form. The description restates 'exploded true/false' and the 'name' default almost verbatim, adding only marginal meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource – show/toggle the exploded view state of the active assembly – with the boolean meaning spelled out inline. It is clear enough to separate from a creation-type sibling, though it does not explicitly contrast with one.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied: call it to explode or collapse the active assembly's view, and supply 'name' only when several views exist. There is no explicit statement of when to prefer another tool or any preconditions (e.g., an active assembly/document must exist).

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