Skip to main content
Glama

DFA Check

dfa_check
Read-only

Grades an assembly's design for manufacturability by calculating assembly efficiency and an ordinal score from part count, fasteners, and handling difficulty, helping compare design variants.

Instructions

Grade an assembly (Boothroyd-Dewhurst-lite). assembly_efficiency = theoretical_min/(part_count+fastener_count) (theoretical_min = unique_part_count or 1); assembly_score scales that by a handling penalty from insertion_axes/ symmetry and decreases monotonically as part/fastener count rises. The grade is an ordinal index for comparing variants (fidelity='correlation', band_pct=None) — rank with it, don't gate on the absolute value. Returns {part_count, fastener_count, insertion_axes, handling_difficulty, assembly_efficiency, assembly_score, symmetry_score, fidelity, band_pct}.

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": {
      "part_count": "<part_count>"
    },
    "name": "dfa_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceNoRun this call in this named workspace
part_countYes
fastener_countNo
insertion_axesNo
unique_part_countNo
symmetric_fractionNo

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 declare readOnlyHint=true and openWorldHint=false, and the description adds meaningful behavioral context about the scoring formula, monotonicity, and the ordinal nature of the result. It also lists the returned fields, which is useful because there is no output schema, though it does not fully explain every penalty detail.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

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

The description is dense but front-loaded and tightly scoped: purpose, formula, interpretation caveat, and return shape appear in a short sequence with no filler. Every sentence contributes useful information for invoking or interpreting the tool.

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?

For a complex scoring tool with no output schema and low schema description coverage, the description does well by explaining the core formula, ordinal interpretation, and returned fields. It is not fully complete because some input parameters remain underspecified, but it provides enough context to call and interpret the tool correctly in most cases.

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 17%, so the description must carry most parameter meaning. It does explain key semantics such as fastener_count in the denominator, unique_part_count as an optional theoretical-minimum source, and insertion_axes/symmetry affecting a handling penalty, but it leaves symmetric_fraction's scale and effect and the workspace parameter largely implicit.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: grade an assembly using a Boothroyd-Dewhurst-lite DFA calculation. The metrics (part_count, fastener_count, assembly_efficiency, assembly_score) make the tool's role clear, though it does not explicitly distinguish itself from the adjacent dfm_check or moldability_check 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?

Gives clear interpretive guidance: the grade is an ordinal index for comparing variants, and the agent should rank with it rather than gate on the absolute value. It also mentions fidelity='correlation' and band_pct=None, but does not name alternatives or state when a different check should be used instead.

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