Skip to main content
Glama

Fit Check

fit_check
Read-only

Classifies a hole/shaft pair as clearance, transition, or interference fit from nominal size and deviations, returning min, max, and nominal clearance plus interference probability.

Instructions

Classify a hole/shaft pair. hole and shaft are {nominal, plus, minus} (signed deviations) or {nominal, tol}. Returns {fit_class:'clearance'| 'transition'|'interference', min_clearance, max_clearance, nominal_clearance, prob_interference} (prob from a normal model with half-band = 3-sigma).

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": {
      "hole": "<hole>",
      "shaft": "<shaft>"
    },
    "name": "fit_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
holeYes
shaftYes
workspaceNoRun this call in this named workspace

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

A3.6/5.0
Behavior4/5

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

With only readOnlyHint and openWorldHint in annotations, the description carries real weight and delivers: it discloses the return fields, the allowed input shapes, and the statistical assumption behind prob_interference (normal model, half-band = 3-sigma). It stops short of stating units or how malformed or ambiguous pairs are rejected.

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?

Three dense sentences, front-loaded with the purpose, then input contract, then return contract. No filler, though the return-type parenthetical is dense enough to read as a schema dump.

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?

Covers purpose, both required inputs, and the full return shape despite there being no output schema. Missing units and any statement of edge-case or error behavior keeps it from being fully self-contained for a nested-object tool.

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?

Schema coverage is only 33% and the hole/shaft objects are bare additionalProperties objects, so the description must compensate, which it does by documenting both accepted forms (nominal/plus/minus signed deviations, or nominal/tol). The workspace parameter is documented in the schema itself, so nothing critical is missing, though units remain unstated.

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?

Uses a specific verb plus resource: 'Classify a hole/shaft pair', which tells an agent exactly what computation happens. It does not, however, distinguish itself from the similarly named sibling fit_class (or fit_page), so the agent must infer which one it wants.

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?

No statement of when to use this versus fit_class, min_clearance, press_fit_stress, or interference_check. The agent must infer the use case purely from the tool name and the input shapes.

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