Skip to main content
Glama

sheet_unfold

Unfold a sheet-metal part into its flat cut blank and report every bend, including allowance, deduction and K-factor source. Build the flat solid for measuring, exporting or nesting.

Instructions

Develop a sheet part into its flat pattern — the blank the part is cut from — and report every bend.

The flat pattern is derived from the bend tree, not reverse-engineered out of the fused solid, so it is exact rather than fitted: each bend contributes its bend allowance BA = angle·(R + K·t), the arc length of the neutral fibre.

k_factor: pins K for every bend. bend_table: a shop's own measured rows [{thickness_mm, inner_radius_mm, angle_deg, allowance_mm | deduction_mm}] — a matching row OUTRANKS the chart, because the shop's press is the ground truth for the shop's press. Without either, K comes from a press-brake corpus keyed by material and r/t. WHICHEVER IT IS, IT IS ECHOED BACK per bend as k_factor + k_source: a flat length whose K you cannot see is a number you cannot check.

build: also create the flat blank as a real solid (holes included) at origin in the XY plane, so it can be measured, exported or nested.

Fidelity: 'exact' only when EVERY bend's K was supplied or table-derived — BA given K is pure arithmetic. One corpus-defaulted bend makes the development a 'correlation' with band_pct, and developed_band_mm gives the resulting millimetre spread of the blank across that K band.

Returns {ok, handle?, name?, volume?, outline, holes, bend_lines, bends, regions, flat_size, flat_bbox, flat_area_mm2, blank_area_mm2, blank_volume_mm3, thickness, material, fidelity, band_pct, developed_band_mm, warnings} — regions being each flat region's polygon, which is what lets the whole report be handed straight back to sheet_refold. Each bend row carries angle_deg, direction, inner_radius_mm, leg_tangent_mm, outer_length_mm, bend_allowance_mm, bend_deduction_mm, outside_setback_mm, k_factor, k_source, and the bend_line / tangent_start / tangent_end segments in flat coordinates. ok=False means the blank cannot be cut as drawn — two feature footprints overlap — with warnings naming which.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoSheetFlat
buildNo
handleYes
originNo
k_factorNo
bend_tableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

No annotations are provided, but the description carries the full burden well: it explains derivation method (bend tree, not reverse-engineered), K factor precedence (bend_table outranks chart), the echo-back contract (k_factor + k_source per bend), ok=False semantics (overlapping footprints), and the build vs. analysis distinction. This is exactly the behavioral context an agent needs.

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?

Front-loaded with the core action, then sections for K, build, fidelity, and returns. It's dense but each paragraph earns its place. Slightly verbose in the returns list, though that's arguably necessary given no output schema.

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 6-param, no-annotation, no-output-schema tool, the description is remarkably complete: it documents the derivation algorithm, parameter precedence, output structure (fields enumerated), failure semantics, and interoperability with sheet_refold. Nothing critical is missing for correct invocation.

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 description coverage is 0%, so the description must compensate — and it does meaningfully: k_factor (pins K), bend_table (shop-measured rows, outranks chart), build (creates a real solid at origin in XY plane), origin usage, and name/handle via context. It doesn't cover every one of the 6 parameters explicitly (e.g., name default), but the ambiguous ones are well explained.

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 ('Develop a sheet part into its flat pattern') and immediately scopes it with 'the blank the part is cut from — and report every bend.' Sibling tools (sheet_refold, sheet_flat_export) are named in the body so the agent can route correctly.

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?

Provides context for when k_factor vs bend_table vs corpus default applies, and distinguishes 'exact' vs 'correlation' fidelity output. It doesn't state explicit when-not-to-use conditions, but the fidelity rules effectively tell the agent when the result is trustworthy.

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