Skip to main content
Glama

Fit Class

fit_class
Read-only

Calculate ISO 286 hole and shaft deviations, minimum and maximum clearances, and interference probability from a fit code (e.g., H7/g6) and basic size in millimeters.

Instructions

ISO 286 limits for a fit code (e.g. 'H7/g6'), in mm. v1 covers a hole-basis H with shaft clearance letters (h, g, f, e). Returns {basic_size, fit, hole:{upper_dev,lower_dev,min,max}, shaft:{...}, fit_class, min_clearance, max_clearance, prob_interference}. Errors on an out-of-table size (>500 mm) or an unsupported code (non-H hole or interference shaft letter).

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": {
      "basic_size": "<basic_size>"
    },
    "name": "fit_class"
  }
}

Input Schema

NameRequiredDescriptionDefault
fitNoH7/g6
workspaceNoRun this call in this named workspace
basic_sizeYes

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.1/5.0
Behavior4/5

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

Annotations already establish read-only and closed-world behavior. The description adds useful non-annotation context: the returned object keys, units, v1 limitations, and explicit error conditions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with the tool's purpose, followed by coverage limits, return shape, and errors. Every sentence carries useful information.

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

Completeness5/5

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

There is no output schema, so the description appropriately describes the return object. It also covers units, supported fit codes, failure modes, and the v1 boundary, which is sufficient for an agent to call and interpret this tool.

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 coverage is only 33%, so the description must compensate. It clarifies the fit code syntax with an example and supported shaft letters, but basic_size is only implied by the mm and >500 mm error context, and workspace semantics come only from the schema.

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?

States a specific calculation: ISO 286 limits for a fit code in mm, including supported v1 scope. It is clearly distinguishable from most modeling siblings, though it does not explicitly contrast with related tools like fit_check or fit_page.

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?

Specifies supported cases (hole-basis H with clearance letters h, g, f, e) and error cases (>500 mm, non-H hole, interference shaft letter), giving clear boundaries for when it applies. It does not name an alternative sibling when the unsupported cases arise.

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