Skip to main content
Glama

DFM Check

dfm_check
Read-only

Screen parts for manufacturability against a pull axis, flagging draft, undercut, and wall-thickness violations; also check sheet-metal bends against press-brake rules.

Instructions

Screen a part for manufacturability against a pull/tool axis. Give a hand-built faces list of {name, draft_deg, wall_mm?} — draft_deg relative to pull_axis (0 = a vertical wall needing draft; <0 = a re-entrant undercut) — OR a live handle, whose per-face descriptors are read off the solid (draft vs the pull axis + a ray-cast undercut test + inward-chord wall sampling) and scored identically (v2 Shape wiring). draft_violations are 0≤draft<min_draft_deg, undercut_faces are draft<0, min_wall_violations are wall_mm<min_wall_mm (defaults by process: injection 1.0, cnc 0.5, sheet/fdm 0.8).

Sheet metal: a handle built by sheet_base/sheet_flange/sheet_tab/sheet_hem is ALSO screened against the press-brake rules (minimum bend radius by material, minimum flange length, hole-to-bend distance, refold collision) with no extra argument — those rules are DELEGATED to the same implementation sheet_check calls, so the two tools cannot return different verdicts on one part. Pass an explicit sheet block {thickness_mm, material?, bends, holes?, interferences?} to screen bends on a part AnkusDrive did not model.

Returns {process, pull_axis, min_wall_mm, draft_violations, undercut_faces, min_wall_violations, score, pass} — plus n_faces + wall_thickness_stats on the handle path, and a sheet sub-result {ok, findings, rules, fidelity, band_pct} whose failures also gate pass on the sheet-metal path.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "dfm_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
facesNo
sheetNo
handleNo
processNoinjection
pull_axisNo+z
workspaceNoRun this call in this named workspace
min_wall_mmNo
min_draft_degNo

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.3/5.0
Behavior5/5

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

Goes well beyond the readOnly annotation: it defines how each face is measured on the handle path (ray-cast undercut test, inward-chord wall sampling), the exact classification rules (0<=draft<min_draft_deg, draft<0), per-process wall defaults, and the fact that sheet rules are delegated to sheet_check so verdicts cannot diverge. It also discloses that sheet sub-result failures gate `pass`, which is decision-critical behavior.

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 core purpose, then organized by input path and by sheet-metal case, and every sentence carries information. It is dense, and the parenthetical detail about ray-casting and chord sampling could be trimmed without losing call guidance.

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?

No output schema exists, so the description supplies the return shape, including the handle-path extras (n_faces, wall_thickness_stats) and the sheet sub-result. For an 8-parameter screening tool with high behavioral complexity, the definition is nearly complete, though it does not explain score/pass thresholds or how `score` is computed.

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 13% with 8 parameters, but the description supplies the semantics that matter: the faces item shape {name, draft_deg, wall_mm?}, draft sign conventions relative to pull_axis, the sheet block fields, and process-dependent min_wall_mm defaults. The remaining gap, mainly min_draft_deg units (though named clearly) and workspace, is minor. Baseline 3 with partial compensation for the coverage gap.

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: screen a part for manufacturability against a pull/tool axis, covering draft, undercut, and wall thickness. It also distinguishes itself from the nearby sheet_check by name and from generic screening tools by describing the two inputs (hand-built faces list vs live handle). An agent can tell what this returns and how it differs from siblings.

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?

Explicitly presents the two mutually exclusive input paths (faces OR handle) and when to pass an explicit sheet block (a part AnkusDrive did not model). It does not explicitly route against adjacent tools such as moldability_check or cnc_machinability_check, so the choice among screening siblings is left implicit.

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