Skip to main content
Glama
inventor-mcp-server

inventor-mcp-server

check_manufacturability

Validates sheet metal parts and assemblies before shop fabrication, flagging bend, flange, hole, sheet-size, and part-clearance problems that need fixing.

Instructions

Can it be made? Run it before a part or assembly goes to the shop.

Active sheet metal part — checked on its flat pattern (made if there is none): the rule (a TXX-VYY shop rule must match the thickness), the flat size against the sheet, every flange against the V die (on both sides of a bend line the sheet must reach V/2 + thickness, to the edge or to the next bend), holes too close to a bend line (nearer than V/2 they are pulled out of shape) and holes smaller than the thickness. Active assembly — parts closer than clearance without touching: no room for the powder coat. Touching parts and fasteners are fine. "problems" is what to fix; "notes" is what was assumed or left unchecked.

Args: v_die: V die opening in mm. 0 = from the rule name (T15-V10 → 10), else 8 x thickness. min_flange: Flat sheet needed beside a bend line, mm. 0 = V/2 + thickness. min_hole_to_bend: Hole edge to bend line, mm. 0 = V/2, or radius + 2 x thickness if more. sheet: Stock sheet, e.g. "2500x1250". Empty = the smallest standard sheet that fits (2000x1000, 2500x1250, 3000x1500) is named. brake_length: Press brake length in mm; 0 = bend length is not checked. clearance: Assembly: smallest gap in mm between parts that don't touch (0.3 for powder coat). parts: Assembly: name patterns, ","-separated, of the parts to look at (default: all).

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": "check_manufacturability"
  }
}

Input Schema

NameRequiredDescriptionDefault
partsNo
sheetNo
v_dieNo
instanceNoWhich connected Inventor to use (list_instances). Leave empty when only one is connected.
clearanceNo
min_flangeNo
brake_lengthNo
min_hole_to_bendNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations at all, the description must carry the full behavioral burden, and it does disclose the key side effect — a flat pattern is created if none exists — plus the fact that touching parts and fasteners are not flagged, and which defaults are inferred (smallest fitting standard sheet, V/2 + thickness). However, it never says whether the operation is otherwise read-only, what it costs on large assemblies, or what happens when the active document is neither a sheet metal part nor an assembly.

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 decision question, then mode-specific checks, then output semantics, then args — a sensible reading order. The prose is dense rather than padded; the parenthetical formula asides are the only place it approaches wordiness.

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 an 8-parameter 0-required tool with an output schema, this covers modes,check semantics, defaults, sentinels and the problems/notes distinction. The remaining gap is the edge case where the active document is neither a sheet metal part nor an assembly, and whether that errors or returns empty.

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?

Schema description coverage is only 13%, so the description has to compensate, and it does so for 7 of the 8 parameters: it gives units, the meaning of the 0 sentinel, the derivation rule (T15-V10 → 10, else 8 x thickness), and the fallback formula for each tolerance. The only undocumented parameter is instance, which the schema itself describes.

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?

"Can it be made?" plus a precise enumeration of the sheet-metal checks (rule vs thickness, flat size vs sheet, flange vs V die, hole-to-bend distance, hole vs thickness) and the assembly clearance check. The verb and resource are unmistakable and scoped to the active document type. It stops short of a fully 5 because it never names the nearest sibling (check_interference) that an agent might otherwise reach for on a clearance question.

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?

"Run it before a part or assembly goes to the shop" gives a concrete trigger, and the description splits behavior by active document type, so an agent knows which mode it will land in. There are no explicit exclusions or named alternatives, so it falls short of the 5 bar.

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