kernelCAD

Flatten Sheet-Metal Pattern

flatten_pattern

Read-onlyIdempotent

Use this when you need the unfolded flat pattern of a bent sheet-metal part. Return the unfolded 2D flat-pattern of a bent sheet-metal Shape as a Region (outer polyline + holes + bend lines + sketch plane). Any number of parallel bends; crossing bends need corner relief. Pass { file } or { code }; optional { featureId } to pick a specific Shape.

Input Schema

Name	Required	Description
`code`	No
`file`	No	Hosted server: cannot read files from your machine — pass `code`, or `project:<slug>` for a saved project.
`featureId`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 11, 2026

removedOutput schema / properties

Removed value: -{
-  "diagnostics": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "ok": {
-    "type": "boolean"
-  },
-  "region": {
-    "additionalProperties": true,
-    "description": "Unfolded flat-pattern Region (outer polyline + holes + bend lines + plane).",
-    "type": "object"
-  }
-}

removedOutput schema / required

Removed value: -[
-  "ok",
-  "diagnostics"
-]

Changed1 schema field changedSep 28, 2026

addedInput schema / properties / file / description

Added value: +"Hosted server: cannot read files from your machine — pass `code`, or `project:<slug>` for a saved project."

Changed1 schema field changedJun 15, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "properties": {
+    "diagnostics": {
+      "items": {
+        "additionalProperties": true,
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "ok": {
+      "type": "boolean"
+    },
+    "region": {
+      "additionalProperties": true,
+      "description": "Unfolded flat-pattern Region (outer polyline + holes + bend lines + plane).",
+      "type": "object"
+    }
+  },
+  "required": [
+    "ok",
+    "diagnostics"
+  ],
+  "type": "object"
+}

First observedMay 25, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond that: the geometric result shape and the geometric limitation around crossing bends. It does not cover error behavior or what happens when the Shape is not sheet-metal, which keeps it below a 5.

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?

Three tight sentences with the purpose, the return shape, the geometric constraint, and the input contract, in that order. Nothing is repeated from the schema and no sentence is filler.

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?

An output schema exists, yet the description still usefully sketches the Region's composition; the input contract and geometric limits are covered. The remaining gap is the unexplained `code` parameter and no hint about failure conditions, which matters somewhat for a zero-required-parameter tool where input selection is ambiguous.

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 only 33% — just the `file` parameter is documented — so the description does real work by stating '{ file } or { code }' mutual exclusivity and explaining that `featureId` picks a specific Shape. However, it never explains what `code` actually is (script source? model code?), leaving one of three parameters opaque in both schema and description.

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: 'Return the unfolded 2D flat-pattern of a bent sheet-metal Shape as a Region'. It also enumerates the Region's contents (outer polyline, holes, bend lines, sketch plane), so an agent knows exactly what operation and output to expect. No sibling tool performs this transformation, and the name/title/description align without redundancy.

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?

'Use this when you need the unfolded flat pattern of a bent sheet-metal part' gives a clear triggering condition, and the note that 'crossing bends need corner relief' pre-empts a failure mode. It stops short of naming when-not-to-use or pointing to an alternative tool, but no sibling is a plausible substitute for flattening.

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.