Skip to main content
Glama

CNC Machinability Check

cnc_machinability_check
Read-only

Screens a solid for 3-axis CNC machinability by counting required setups and flagging undercuts, deep pockets, small radii, and thin walls without CAM toolpaths.

Instructions

3-axis CNC machinability screen off a live solid — pure geometry, NO CAM engine (no toolpath, no gouge check, no holder collision).

Counts SETUPS from a tool-approach census: for every machined face, which of ±X/±Y/±Z can both address it (the normal does not point away — a wall parallel to the tool axis is milled by the cutter's periphery) and reach it (a ray from the face escapes the solid, the same caster the moldability undercut check uses), reduced to a minimum cover. Faces lying on the stock envelope are excluded: they are billet surfaces, and counting them would quote six setups for a plain block.

Findings: 'undercut' (a machined face no principal approach reaches — 5-axis, a special cutter, or a redesign), 'deep_pocket' (depth/(2·corner radius) past max_l_over_d — the corner radius caps the cutter and it cannot reach), 'small_radius' (an internal corner below the smallest cutter quoted, including a SHARP planar corner reported as radius 0, which no rotating tool can produce), 'thin_wall'. pass is false when any fires; more than max_setups is a warning, not a failure. fidelity='correlation', band_pct=None (an ordinal screen — rank variants with score, don't gate on it).

Returns {setups, setup_directions, coverage, machined_faces, stock_faces, machined_area_mm2, min_internal_radius_mm, max_l_over_d_seen, undercut_faces, findings:[{code, severity, feature, detail}], warnings, score, pass, fidelity, band_pct, basis, escalate_to='cnc_time_estimate', limitations, n_faces}.

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": {
      "model": "<model>"
    },
    "name": "cnc_machinability_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
modelYes
workspaceNoRun this call in this named workspace
max_setupsNo
min_wall_mmNo
max_l_over_dNo
min_tool_radius_mmNo

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

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

Annotations already declare readOnlyHint=true and openWorldHint=false, yet the description still delivers substantial extra behavior: the exact census algorithm for counting setups, the exclusion of stock-envelope faces (with the rationale that counting them would quote six setups for a block), the meaning of each finding code, and the fact that pass is false only on a finding while excess setups is merely a warning. It also self-labels fidelity='correlation' with band_pct=None and enumerates limitations.

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?

The most decision-relevant statement — what the tool is and is not — is front-loaded in the first sentence, followed by method, findings, and return shape in a sensible order. It is dense with parentheticals and long clauses, which costs some readability, but nearly every sentence carries information an agent needs (setup census rules, finding semantics, fidelity caveat).

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?

With no output schema, the description correctly enumerates the return payload field-by-field (setups, coverage, findings shape, score, pass, fidelity, escalate_to, limitations), which is exactly what an agent needs. The residual gap is the required 'model' handle and the 'workspace' parameter, whose accepted forms are never stated, and min_wall_mm's threshold role is left implicit.

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?

With only 17% schema coverage, the description carries most of the burden and does well: max_setups is redefined ('more than max_setups is a warning, not a failure'), max_l_over_d gets a concrete formula ('depth/(2·corner radius)'), and min_tool_radius_mm is tied to 'the smallest cutter quoted' and small_radius findings. min_wall_mm is only implicitly linked to 'thin_wall', and the required model argument is never described.

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?

Opens with a specific verb and resource: '3-axis CNC machinability screen off a live solid — pure geometry, NO CAM engine', immediately scoping what it is not (no toolpath/gouge/holder collision). It is clearly distinguished from the many sibling checks (moldability_screen, dfm_check, cnc_time_estimate) by the setup-count/principal-approach framing.

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 real usage context: it names the escalation target (escalate_to='cnc_time_estimate') and states explicitly that this is an ordinal screen — 'rank variants with `score`, don't gate on it'. It also notes the tolerances (max_setups is a warning, not a failure). It stops short of explicitly saying when to prefer moldability_screen or dfm_check instead, but the boundary with cnc_time_estimate is clear.

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