Skip to main content
Glama

Sheet Hem

sheet_hem

Folds a sheet-metal edge back 180° into a closed or open hem to stiffen the free edge and bury the sharp cut line for safe handling, with optional radius or gap overrides.

Instructions

Fold a hem back on itself — the 180-degree return that stiffens a free edge and buries the sharp cut line so the part is safe to handle.

kind: 'closed' (inside radius t/2, gap t) or 'open' (radius t, gap 2t). radius_mm / gap_mm: override the style directly; the gap between the returned leg and the parent is exactly 2R, so gap wins as radius = gap/2.

length_mm is ALWAYS the return leg measured from the end of the bend: a 180-degree bend has no virtual apex to dimension to — the outside surfaces are parallel and never meet — so an 'outer' dimension would be infinite. For the same reason a hem reports a bend allowance but no bend deduction, and sheet_check screens it as a two-hit hem (bend, then flatten in a hemming die) exempt from the air-bend radius and flange rules. A teardrop hem wraps past 180 degrees and is out of scope.

Returns the same dict sheet_flange does, plus {hem_kind, gap_mm}.

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>",
      "edge": "<edge>",
      "length_mm": "<length_mm>"
    },
    "name": "sheet_hem"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeYes
kindNoclosed
nameNoSheetHem
gap_mmNo
handleYes
width_mmNo
directionNoup
length_mmYes
offset_mmNo
radius_mmNo
workspaceNoRun this call in this named workspace
feature_nameNo

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 establish that this is a non-read-only, non-destructive operation, but the description adds meaningful domain behavior: the 180-degree return geometry, the absence of bend deduction, interaction with sheet_check, and exclusion of teardrop hems. It still does not discuss permissions or exact mutation effects, but the added context is substantial.

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 front-loaded with the core operation and then gives relevant geometric and manufacturing context. It is somewhat dense and longer than a minimal definition, but most of the detail earns its place by clarifying non-obvious hem behavior.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 12-parameter sheet-metal operation with no output schema and very low schema description coverage, the definition covers the hem-specific semantics and return shape but omits meaning for several parameters. It is adequate for understanding the operation, but not fully complete for an agent invoking it without prior schema context.

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 description coverage is only 8%, so the description must compensate for many undocumented parameters. It does explain the important hem-specific parameters well—kind, radius_mm, gap_mm, and especially length_mm—but leaves required parameters like handle and edge, plus width_mm, offset_mm, and direction, largely unexplained.

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 description states a specific verb and resource: folding a hem back on itself as a 180-degree return. It also distinguishes the operation from related sheet-metal features by explaining that a hem has no virtual apex and reports bend allowance but no bend deduction.

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 clear context for when this geometry applies and explicitly excludes teardrop hems as out of scope. However, it does not explicitly compare when to use this tool versus sheet_flange or other sheet-metal siblings.

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