Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

create_exploded_view

Creates an exploded view of the active assembly configuration by moving specified components along assembly axes in ordered steps, returning the view name and measured moves.

Instructions

Make a new exploded view of the active assembly's configuration: steps move components along the assembly axes (direction +x, -x, +y, -y, +z or -z; distance required). Components are named as in list_components (a path such as Sub-1/Part-1 for a part in a sub-assembly). The view is left shown exploded (show_exploded collapses it); while it is shown, mates, measurements, check_interference and export_stl see the exploded positions, so collapse it first. Mates are not changed. Returns the view's name and each component's measured move per step.

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": {
      "steps": "<steps>"
    },
    "name": "create_exploded_view"
  }
}

Input Schema

NameRequiredDescriptionDefault
unitNomm, cm, m, inch or ft
stepsYesThe steps in order: [{components: [...], direction: '+z', distance: 50}]

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

With no annotations supplied, the description carries the full burden and does so: it discloses the persistent side effect (view left exploded), the downstream tools whose results change, the guarantee that mates are not modified, and the return payload (view name plus each component's measured move per step).

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?

Content is front-loaded: what it creates, then naming, then side effects, then invariants, then return value. The parenthetical enumerations of directions and paths make sentences dense but every clause carries information an agent needs.

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 two-parameter mutation tool with no annotations and no output schema, the description covers purpose, side effects, invariants, naming, and return values. Nothing required to invoke it correctly or to interpret the result 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%, so the baseline is 3, but the description adds real meaning beyond the schema by specifying the component naming convention (a path such as Sub-1/Part-1 as produced by list_components) and reiterating that distance is required per step. The unit parameter is left unexplained, which keeps it from a 5.

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?

The definition opens with a specific verb and resource: creating a new exploded view of the active assembly's configuration. It clearly separates itself from show_exploded, which is identified as the collapse counterpart, so an agent can distinguish the two without inspecting schemas.

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?

It states the operational rule explicitly: the view is left shown exploded, show_exploded collapses it, and mates, measurements, check_interference and export_stl read exploded positions while it is shown, so collapse first. That is concrete when-to-use and when-not guidance tied to named sibling tools.

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