Skip to main content
Glama

Press Fit Stress

press_fit_stress
Read-only

Calculate interference (press/shrink) fit contact pressure, hub hoop stress, torque capacity, axial force, and hub yield safety factor from shaft/hub dimensions, interference, and material properties.

Instructions

Rate an interference (press/shrink) fit via Lamé. p=delta_r E (ro^2-rc^2)/ (2 rc ro^2); hub bore hoop=p(ro^2+rc^2)/(ro^2-rc^2); torque=2pi mu p rc^2 L. interference_mm is diametral.

E comes from material's Materials-DB card; youngs_modulus_mpa overrides it. Every output is LINEAR in E, so a material the corpus has no modulus for is an ERROR, not an assumption (#269) — the message names both exits.

pass is THREE-state: the hub yield check needs the card's yield_mpa, and a card without one (Fused-Silica, Gold, Concrete, ...) leaves the check unperformed. That returns pass=null with the reason in warnings — an unperformed check is not a passed one. Test pass is True, not truthiness.

Returns {contact_pressure_mpa, hub_hoop_stress_mpa, torque_capacity_nm, axial_force_n, hub_yield_sf, youngs_modulus_mpa, youngs_basis, hub_yield_basis, pass, warnings}.

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": {
      "shaft_dia_mm": "<shaft_dia_mm>",
      "hub_outer_dia_mm": "<hub_outer_dia_mm>",
      "interference_mm": "<interference_mm>",
      "engagement_length_mm": "<engagement_length_mm>"
    },
    "name": "press_fit_stress"
  }
}

Input Schema

NameRequiredDescriptionDefault
materialNoSteel-A36
workspaceNoRun this call in this named workspace
shaft_dia_mmYes
friction_coefNo
interference_mmYes
hub_outer_dia_mmYes
youngs_modulus_mpaNo
engagement_length_mmYes

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

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

With only readOnlyHint available, the description carries the burden well: it discloses that a missing modulus is a hard ERROR, that `pass` is three-state and can be null when yield_mpa is absent, that unperformed checks emit warnings, and it names the two basis fields so the agent can audit assumptions. It also enumerates the full return structure.

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-loads the purpose and formulas before the edge-case semantics, and every sentence carries operative information (error condition, three-state test, return keys). It is dense — the inline math and the issue-number reference add reading cost — but not padded.

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?

No output schema exists, yet the description lists all ten return fields and explains the nullability of `pass` and the two basis fields. For an 8-parameter, read-only computational tool this is sufficient to call and interpret it correctly.

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 13%, so the description must compensate, and it does for the highest-risk ambiguity: interference_mm is explicitly diametral, youngs_modulus_mpa is an override of the material card, and the formulas expose what rc, ro, L and mu mean. It leaves workspace and the shaft/hub diameter roles to inference.

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 verb and resource — 'Rate an interference (press/shrink) fit via Lamé' — plus the exact governing equations, so the agent knows precisely what physical check this performs. It does not, however, distinguish itself from siblings like fit_check, fit_class, or hertz_contact, which an agent must choose between.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the physics it computes (press/shrink fit stress and torque capacity), but there is no explicit statement of when to pick this over fit_check or fit_class, nor any precondition guidance beyond the material-card requirement. The material-sourcing rule is the only concrete 'how/when' instruction.

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