Skip to main content
Glama

compute_iso_fit

Read-only

Calculates ISO 286 hole and shaft limits, fits, and clearance for a nominal diameter, then checks whether the fit is achievable on an FDM printer using material shrinkage and calibration data.

Instructions

ISO 286 limits and fits with FDM achievability gate.

Needs Kiln Pro.

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": {
      "nominal_mm": "<nominal_mm>"
    },
    "name": "compute_iso_fit"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo"normie" (plain English), "engineer" (full math), or "auto" (infer from brief). Default: "auto".
briefNoOptional user request brief (auto-detects engineer mode if it contains FoS / sigma / ISO 286 / etc.).
materialNoFDM material name (for shrinkage compensation). Default: "PLA".
grade_holeNoHole IT grade. 5 to 12 for "A" to "H", "J" and "Js"; 4 to 7 for "K", "M" and "N" (others are refused). Default: 7.
hole_classNoHole fundamental deviation letter, uppercase: "A" to "H" ("H" most common), "J", "Js", "K", "M" or "N". "P" and beyond are refused. Default: "H".
nominal_mmYesNominal diameter in mm.
printer_idNoPrinter identifier (e.g. "bambu_a1") to look up calibration for. When supplied, the response quotes a tighter or wider feasibility band based on the calibration tier.
grade_shaftNoShaft IT grade. 5 to 12 for "a" to "h", "j" and "js"; 4 to 7 for "k" to "u" (others are refused). Default: 6.
shaft_classNoShaft fundamental deviation letter, lowercase: "a" to "h", "j", "js", "k", "m", "n", "p", "r", "s", "t" or "u". Default: "h".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv1.5.1
    • addedInput schema / properties / brief / description
      Added value: +"Optional user request brief (auto-detects engineer mode if it contains FoS / sigma / ISO 286 / etc.)."
    • changedInput schema / properties / grade_hole / description
      Previous value: -"Default: 7."New value: +"Hole IT grade.  5 to 12 for \"A\" to \"H\", \"J\" and \"Js\"; 4 to 7 for \"K\", \"M\" and \"N\" (others are refused). Default: 7."
    • changedInput schema / properties / grade_shaft / description
      Previous value: -"Default: 6."New value: +"Shaft IT grade.  5 to 12 for \"a\" to \"h\", \"j\" and \"js\"; 4 to 7 for \"k\" to \"u\" (others are refused). Default: 6."
    • changedInput schema / properties / hole_class / description
      Previous value: -"Default: \"H\"."New value: +"Hole fundamental deviation letter, uppercase: \"A\" to \"H\" (\"H\" most common), \"J\", \"Js\", \"K\", \"M\" or \"N\".  \"P\" and beyond are refused. Default: \"H\"."
    • changedInput schema / properties / material / description
      Previous value: -"Default: \"PLA\"."New value: +"FDM material name (for shrinkage compensation). Default: \"PLA\"."
    • changedInput schema / properties / mode / description
      Previous value: -"Default: \"auto\"."New value: +"\"normie\" (plain English), \"engineer\" (full math), or \"auto\" (infer from brief). Default: \"auto\"."
    • addedInput schema / properties / nominal_mm / description
      Added value: +"Nominal diameter in mm."
    • addedInput schema / properties / printer_id / description
      Added value: +"Printer identifier (e.g. \"bambu_a1\") to look up calibration for.  When supplied, the response quotes a tighter or wider feasibility band based on the calibration tier."
    • changedInput schema / properties / shaft_class / description
      Previous value: -"Default: \"h\"."New value: +"Shaft fundamental deviation letter, lowercase: \"a\" to \"h\", \"j\", \"js\", \"k\", \"m\", \"n\", \"p\", \"r\", \"s\", \"t\" or \"u\". Default: \"h\"."
  2. Addedv1.5.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds two genuinely useful non-annotation facts: the result includes an FDM achievability gate (a feasibility judgement on top of the ISO numbers) and the tool requires Kiln Pro. It does not say how the gate behaves when a fit is unachievable (refusal vs. flagged result) or what the returned bands look like.

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?

Two short lines with no filler and the core capability front-loaded. The stray blank line and the terse noun-phrase opening ('ISO 286 limits and fits...') rather than an action verb cost it the top score, but nothing 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?

This is a nine-parameter domain-specific calculation with no output schema, and the description never says what comes back — hole/shaft limit dimensions, selected fit type, the achievability verdict, or per-printer tighter/wider bands hinted at by printer_id. The tier prerequisite is the only operational context supplied, leaving the response contract entirely implicit.

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 100% and the schema is unusually rich — it documents mode, material, hole/shaft grade ranges with refusal rules, deviation letters, and the printer_id calibration effect. The description adds nothing about any of these nine parameters, so baseline 3 is appropriate; the schema is doing all the work.

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 names a specific engineering computation (ISO 286 limits and fits) plus a distinguishing extra step ('FDM achievability gate'), which tells an agent this is a standards-based fit calculator with a printability verdict, not just a generic tolerance tool. It stops short of explicitly differentiating from close siblings such as tolerance_stack_analysis, recommend_hole, or recommend_running_clearance.

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?

The only guidance is a prerequisite, 'Needs Kiln Pro', which tells the agent about a tier gate but nothing about when to reach for this tool versus sibling fit/hole tools. There is no when-to-use, when-not-to-use, or alternate-tool routing guidance at all.

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