Skip to main content
Glama

Sheet Check

sheet_check
Read-only

Screens sheet parts for press-brake manufacturability by checking minimum bend radius, flange length, hole-to-bend clearance, and refold collisions.

Instructions

Press-brake manufacturability screen for a sheet part — four rules, each with the number it came from:

min_bend_radius — an inside radius below the material's minimum (a corpus value per material: 3t for 6061-T6, 1t for A36, 0.5t for annealed 1100) cracks the outer fibre. min_flange_length — an outer leg under 4t + R has no die shoulder to sit on and dives into the vee. hole_to_bend — a hole whose EDGE is nearer the bend tangent than 2t + R draws into an oval. Holes are read off the real solid, not declared. refold_collision — two features that occupy the same space once folded, found by actually intersecting them rather than by a rule.

A hem is screened as a two-hit hem (bend, then flatten) and exempted from the air-bend radius and flange rules, which would otherwise fail every hem ever drawn. A flat pattern whose feature footprints overlap is a finding too, not a warning dropped on the floor. An unrecognised material degrades to a bend-class fallback WITH an info finding saying so, rather than skipping the rule silently.

min_flange_t / hole_to_bend_t: override the thresholds (multiples of thickness).

fidelity='correlation' with band_pct=None — these are press-brake rules of thumb, thresholds for ranking and gating rather than measured predictions.

Returns {ok, findings, fail_count, rules, min_bend_radius_mm, min_bend_radius_source, flat_size, blank_area_mm2, k_factors, thickness_mm, material, fidelity, band_pct}. Each finding carries {code, severity, message} plus the measured value and the limit it missed.

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>"
    },
    "name": "sheet_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYes
k_factorNo
workspaceNoRun this call in this named workspace
bend_tableNo
min_flange_tNo
hole_to_bend_tNo

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
Behavior5/5

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

Annotations only declare readOnlyHint=true and openWorldHint=false; the description goes far beyond that. It discloses the hem-exemption behaviour ('screened as a two-hit hem ... exempted from the air-bend radius and flange rules'), the silent-failure mitigation ('an unrecognised material degrades to a bend-class fallback WITH an info finding'), the fact that flat-pattern footprint overlap is a finding rather than a dropped warning, and that holes/collisions are measured off the real solid rather than declared. These are exactly the behavioural traits an agent could not get from the annotations or schema.

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 long but organized: purpose first, then a scannable rule list, then override and fidelity notes, then the return shape. Nearly every sentence carries information an agent needs; only minor color ('dives into the vee', 'warning dropped on the floor') could be trimmed without loss.

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 usefully enumerates the return object (ok, findings, fail_count, rules, min_bend_radius_mm, min_bend_radius_source, flat_size, k_factors, etc.) and the per-finding shape, and it resolves the ambiguity of fallback and hem behaviour. It is short of complete only on input-side questions — what a handle refers to, how bend_table is supplied, and what k_factor changes.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 17%, so the description carries most of the burden, and it only partly does so: it explains min_flange_t and hole_to_bend_t as thickness-multiple threshold overrides. The required handle, k_factor, bend_table, and workspace get no explanation at all, and the description discusses fidelity/band_pct which do not appear in the input schema, muddying rather than clarifying the parameter set.

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 first sentence names the operation precisely: 'Press-brake manufacturability screen for a sheet part — four rules,' then enumerates each rule (min_bend_radius, min_flange_length, hole_to_bend, refold_collision) with its physical basis. This is clearly differentiated from the modeling siblings (sheet_flange, sheet_unfold) and from adjacent checks like plate_check or dfm_check, which do not screen bend radii or refold collisions.

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?

The intended context — screening a sheet part before release — is implied by the rule set and by the 'correlation fidelity, ranking and gating rather than measured predictions' caveat. However, it never states when to call sheet_check versus dfm_check, plate_check, or cnc_machinability_check, nor any prerequisite (e.g., that the part must already be modeled and foldable). Usage is inferable but not explicit.

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