Skip to main content
Glama

Sheet Flange

sheet_flange

Bends a flange along a straight free edge of a sheet part, with control over angle, direction, radius, and length reference for sheet-metal design.

Instructions

Bend a flange off a free edge of a sheet part.

edge: a stable e_* tag from list_edges (or 'EdgeN'/int) on a STRAIGHT free edge of a flat region — a bend line is the intersection of two planes, so an arc cannot carry one and is rejected. angle_deg: the bend angle, i.e. the deviation from flat, so 90 is a right-angle flange. Must be in (0, 180]. inner_radius_mm: inside bend radius; defaults to the material thickness. direction: 'up' (toward the region's outward normal) or 'down'. length_from: what length_mm measures — the number most often misread on a sheet drawing. 'outer' (default) to the outside virtual apex, which is what a drawing dimension normally means; 'inner' to the inside apex; 'tangent' for the straight leg past the end of the bend. width_mm / offset_mm: narrow the flange to part of the picked edge. k_factor: pins K for THIS bend only. Leave it unset and the choice defers to sheet_unfold — the folded solid does not depend on K at all, only the flat pattern does.

Consumes the input handle (it is hidden, having become part of the result).

Returns {handle, name, feature, kind, volume, angle_deg, inner_radius_mm, leg_tangent_mm, length_from, direction, span_mm, thickness_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_flange"
  }
}

Input Schema

NameRequiredDescriptionDefault
edgeYes
nameNoSheetFlange
handleYes
k_factorNo
width_mmNo
angle_degNo
directionNoup
length_mmYes
offset_mmNo
workspaceNoRun this call in this named workspace
length_fromNoouter
feature_nameNo
inner_radius_mmNo

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/5.0
Behavior4/5

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

Annotations already declare a non-read-only, non-destructive, closed-world mutation, so the safety profile is covered. The description adds genuinely non-obvious behavior: the input handle is consumed and hidden, arcs are rejected, and K only affects the flat pattern rather than the folded solid. It doesn't mention permissions or what happens on failure, hence not 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.

Conciseness4/5

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

Front-loaded with the action, then parameter-by-parameter notes that each add real information rather than restating the schema. It is longer than typical, but the length is justified by 13 under-documented parameters; the aside about drawings misreading length_from is useful rather than filler.

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 mutation tool with no output schema and a nearly undescribed schema, the description supplies the return shape inline ({handle, name, feature, kind, volume, angle_deg, ...}) and flags the consumed-handle side effect. Nothing an agent needs to call it correctly and interpret the result is missing.

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

Parameters5/5

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

With only 8% schema description coverage across 13 parameters, the description carries the load and does so well: it defines edge tag format and validity, the deviation-from-flat meaning of angle_deg and its (0,180] range, inner_radius default, up/down direction semantics, the easily-misread length_from options, and the narrowing role of width_mm/offset_mm. Only handle/name/feature_name/workspace go unelaborated, and those are conventional.

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 ('Bend a flange off a free edge of a sheet part') and constrains the target to a straight free edge of a flat region, which implicitly separates it from siblings like sheet_tab and sheet_hem. An agent can identify the operation and the exact kind of geometry it applies to without opening the schema.

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?

Gives clear preconditions (a bend line must be the intersection of two planes, so arcs are rejected) and routing guidance for k_factor ('leave unset and the choice defers to sheet_unfold'). It stops short of explicitly naming which sibling to use instead when the edge is an arc or when the intent is a tab rather than a flange.

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