Skip to main content
Glama
FullyDefined – AI for SOLIDWORKS

FullyDefined – AI for SOLIDWORKS

hem

Folds sheet metal edges back on themselves into closed, open, or teardrop profiles, letting you set gap, angle, radius, or folded-leg length and return added volume.

Instructions

Fold a sheet metal edge back on itself (a hem), inside the old edge: closed, open (with a gap) or teardrop (angle, default 200 degrees; radius, default the part's). length is the folded-back leg of a closed or open hem (a teardrop has none). Returns the volume added. Refused while flattened.

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": {
      "edge": "<edge>",
      "type": "<type>"
    },
    "name": "hem"
  }
}

Input Schema

NameRequiredDescriptionDefault
gapNoGap of an open hem (default 1 mm)
edgeYesA point on the edge (within 0.5 mm)
typeYesKind of hem
unitNomm, cm, m, inch or ft
angleNoTeardrop only: roll angle in degrees, 181-225 (default 200)
lengthNoLength of the folded-back leg
radiusNoTeardrop only: radius (default: the part's bend radius)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the key traits: the operation is a mutation that returns the volume added, and it is refused on a flattened part. It stops short of stating reversibility, permission requirements, or what happens to adjacent bends, which keeps it below a 5 for an unannotated mutation tool.

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?

Four tight sentences, front-loaded with the action and variant list before parameter semantics, return value, and the refusal condition. The nested parentheses (especially around teardrop defaults) make it slightly denser than it needs to be, but no sentence is 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?

No output schema exists, and the description supplies the return value ('volume added'); the refusal state covers the main failure mode; and the seven parameters are fully documented in the schema. For a 7-parameter nested-object mutation tool, nothing essential is missing.

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 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: length applies only to closed/open hems and 'a teardrop has none', and radius defaults to the part's bend radius rather than an absolute value. That conditional relationship is real semantic value beyond the field-level descriptions.

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 — 'Fold a sheet metal edge back on itself (a hem)' — and immediately enumerates the three variants (closed, open, teardrop). An agent can tell this apart from adjacent edge operations like chamfer_edges 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the operation itself, and the precondition 'Refused while flattened' tells the agent when the call will not work. However, there is no explicit 'use this when you need X instead of Y' routing, nor any statement of prerequisites (e.g. that the part must be a sheet metal body).

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