kernelCAD

Plan Exploded View

explode_view

Read-onlyIdempotent

Use this when you need an ordered exploded-view plan for an assembly. Supply parts as {name,center:[x,y,z],size:[x,y,z]} in mm. Optional assembly_order sets the sequence; missing order falls back to input part order, and unlisted/unknown order refs are reported. Choose mode axis (default) or radial; axis follows the requested direction, radial moves parts away from the assembly centroid. The result includes ready-to-paste param_declarations, animation_tracks and reverse_animation_tracks for animationView(), part_transforms for existing shapes, and script_fragment. cameraPlan gives framing guidance.

Input Schema

Name	Required	Description
`axis`	No	Assembly direction; default +Z.
`mode`	No	Explode direction strategy; default axis.
`parts`	No	Named assembly parts and measured bbox centers/sizes in mm.
`spacing`	No	Positive spacing scale; default 1.25.
`duration_ms`	No	Timeline duration from 500 to 60000 ms; default 3000.
`assembly_order`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

removedInput schema / properties / handoff

Removed value: -{
-  "additionalProperties": true,
-  "description": "Optional handoff metadata. Assembly order lookup supports assembly_order or assembly.order.",
-  "type": "object"
-}

changedInput schema / properties / parts / description

Previous value: -"Named assembly parts and measured bbox centers/sizes in mm. Optional when handoff is supplied."New value: +"Named assembly parts and measured bbox centers/sizes in mm."

AddedOct 16, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent planning operation. The description usefully adds behavioral details: assembly_order fallback to input order, reporting of unknown order references, axis versus radial movement semantics, and the exact output artifacts generated.

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?

The description is a dense but front-loaded paragraph with no empty filler. It could be slightly more scannable, but every clause contributes useful planning or invocation context.

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?

Given the output schema and strong annotations, the description is complete enough for an agent to call the tool correctly. It explains inputs, optional fallback behavior, mode semantics, and the major returned artifacts.

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 high at 83%, so most parameter meaning is already documented. The description still adds value by clarifying the expected part tuple format, assembly_order fallback/reporting behavior, and how mode changes the explosion strategy.

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?

The description clearly states a specific verb and resource: producing an ordered exploded-view plan for an assembly. It is distinct from most sibling tools, but it does not explicitly contrast itself with related tools such as capture_animation or blockout_assembly.

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?

It gives a clear triggering condition: use when you need an ordered exploded-view plan for an assembly. It does not name alternatives or state when not to use it, so it falls short of full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All kernelCAD tools Inspect

Try in Browser

Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.