Skip to main content
Glama

Sheet Flat Export

sheet_flat_export
Destructive

Export a sheet-metal flat pattern as a layered DXF with CUT, BEND_UP and BEND_DOWN layers, so laser, punch and press-brake shops get a ready-to-quote, ready-to-cut file.

Instructions

Write the flat pattern as a LAYERED DXF — the file a laser, punch or press-brake shop actually quotes and cuts from. This is the deliverable the whole sheet-metal family exists to produce.

Three layers, because a flat pattern without them is not a shop deliverable: CUT carries the closed outer profile and every hole; BEND_UP and BEND_DOWN carry one centreline per bend, so the operator reads the fold direction off the print rather than inferring it. DXF R12 ASCII in millimetres, written directly rather than through TechDraw — a flat pattern is not a drawing view and does not want a sheet frame, a scale or a title block around it. path must end in .dxf.

Takes the same k_factor / bend_table arguments as sheet_unfold, since the outline it writes IS the development.

Returns {ok, path, size, layers, entities, flat_size, blank_area_mm2, bends (with bend_allowance_mm, bend_deduction_mm, k_factor and k_source per bend), fidelity, band_pct, warnings}.

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": {
      "handle": "<handle>",
      "path": "<path>"
    },
    "name": "sheet_flat_export"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYes
handleYes
k_factorNo
workspaceNoRun this call in this named workspace
bend_tableNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.5.7
    • addedInput schema / properties / workspace
      Added value: +{
      +  "default": "",
      +  "description": "Run this call in this named workspace",
      +  "title": "Workspace",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare a non-read-only, destructive, closed-world write; the description adds the concrete behavior an agent needs — three named layers with defined contents, DXF R12 ASCII, millimetres, bypassing TechDraw, and a hard constraint that `path` must end in .dxf. It omits overwrite semantics for an existing file, which is the one destructive behavior still undisclosed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the verb and artifact, and the layer/format paragraph is dense with usable detail. However, the framing sentences ('the file a laser, punch or press-brake shop actually quotes and cuts from', 'the deliverable the whole sheet-metal family exists to produce') are promotional filler that could be cut without losing instruction.

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?

With no output schema, the description compensates by enumerating the return payload (path, size, layers, entities, flat_size, blank_area_mm2, per-bend allowance/deduction/k_factor/k_source, fidelity, band_pct, warnings), which is unusually thorough. Missing only the handle's role and overwrite/error behavior.

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 only 20% (just `workspace`), so the description must compensate, and it does for the ambiguous ones: `path` requires a .dxf suffix, and `k_factor`/`bend_table` follow sheet_unfold because the written outline IS the development. Only `handle` is left unglossed, which is consistent across the entire sibling family.

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 (write) and a specific artifact (a layered DXF flat pattern) with its units and dialect (R12 ASCII, millimetres). It explicitly separates itself from siblings like export_drawing/TechDraw by explaining that a flat pattern is not a drawing view and carries no sheet frame, scale or title block.

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?

It positions itself as the terminal deliverable of the sheet-metal family and points at sheet_unfold for the shared k_factor/bend_table semantics, which implies the routing (unfold to develop, export to deliver). But it never states when to prefer it over export_shape or export_drawing, nor any precondition such as needing a prior unfold/refold state.

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