Skip to main content
Glama
formastep-mcp
by eldertek

dfm_audit

Read-onlyIdempotent

Audit a PartSpec or mesh file for manufacturability by checking watertightness, wall thickness, overhangs, and BOM against a selected process.

Instructions

Run DFM QA checks (watertightness, wall thickness, overhangs, BOM) on a PartSpec or mesh file.

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_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
specNo
processNofdm
mesh_pathNo
min_wall_mmNo
max_overhang_degNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds the set of checks performed, which is useful behavioral context, but it omits what happens when both spec and mesh_path are omitted (all five parameters are optional) and says nothing about cost or runtime. Adequate but with a real gap around input resolution.

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?

A single front-loaded sentence with no filler, and the enumerated checks are easy to scan. It is arguably under-sized for a five-parameter tool with zero schema descriptions, but nothing in the text is wasted.

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

Completeness2/5

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

An output schema exists, so return values need not be described, but with five undocumented parameters from a 0% coverage schema and no required field, the description should clarify how inputs combine (spec vs mesh_path) and what the process parameter controls. As written, an agent must guess the input contract.

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

Parameters2/5

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

Schema description coverage is 0%, so the description must carry the burden, and it only maps loosely to two parameters ('PartSpec' → spec, 'mesh file' → mesh_path). It says nothing about the process enum (fdm/sla/cnc/injection/sheet), min_wall_mm, or max_overhang_deg, leaving threshold behavior and default 45 degrees unexplained beyond the schema's raw defaults.

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?

The description gives a specific verb ('Run DFM QA checks') and resources ('PartSpec or mesh file'), and enumerates the checks (watertightness, wall thickness, overhangs, BOM), which clearly separates it from siblings like part_build or export_manufacturing_bundle. It does not explicitly name an alternative tool, but the purpose is unambiguous 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says whether this should be run before part_build, after step_inspect, or only for certain processes. The phrase 'on a PartSpec or mesh file' hints at two input modes but does not state that one is required or when to prefer each.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.