Skip to main content
Glama

Fatigue Check

fatigue_check
Read-only

Calculate fatigue life and safety factor from stress range, mean stress, and material data using S-N curves with Goodman mean-stress correction; returns pass/fail for required cycles.

Instructions

Rate fatigue life (S-N Basquin + Goodman mean-stress correction). σ_a = stress_range/2; infinite-life SF = 1/(σ_a/σ_e + σ_m/σ_uts); finite life from an equivalent fully-reversed amplitude on a log-log S-N line. σ_e/σ_uts come from the material (or overrides). pass = survives cycles (σ_ar ≤ σ_e ⇒ infinite life); a tensile mean ≥ σ_uts fails outright. Returns {stress_amplitude_mpa, mean_stress_mpa, endurance_mpa, uts_mpa, equiv_reversed_mpa, safety_factor, life_cycles, required_cycles, pass, governing_mode, endurance_basis}.

The S-N line runs from (1e3, s1000_fraction·UTS) to (endurance_cycles, σ_e). Both default to the steel convention (0.9 and 1e6); aluminium and other non-ferrous alloys have no true endurance knee, so set endurance_cycles to the life the quoted σ_e was measured at (commonly 5e8).

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": {
      "stress_range_mpa": "<stress_range_mpa>"
    },
    "name": "fatigue_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
cyclesNo
uts_mpaNo
materialNoSteel-1045
workspaceNoRun this call in this named workspace
endurance_mpaNo
s1000_fractionNo
mean_stress_mpaNo
endurance_cyclesNo
stress_range_mpaYes

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?

With readOnlyHint already covering safety, the description adds substantive behavior: failure semantics (tensile mean ≥ σ_uts fails outright), the pass rule (σ_ar ≤ σ_e ⇒ infinite life), the S-N line endpoints, and default conventions that affect results. Minor gap: no note on numeric precision, domain of validity, or warning when inputs imply extrapolation beyond the S-N line.

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-loaded with the purpose and return shape, then the modelling conventions. The formula-dense sentences pack a lot of meaning per line, though the S-N paragraph is somewhat compressed and requires domain fluency to parse quickly.

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?

No output schema exists, yet the description enumerates all returned keys (stress_amplitude_mpa, safety_factor, pass, governing_mode, etc.), which is exactly what is needed. Combined with the failure and pass rules, an agent can call and interpret it correctly; only edge-case behaviors (out-of-range inputs, material name resolution failures) are unstated.

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 11%, so the description must carry the load — and it largely does: it defines σ_a = stress_range/2, explains that σ_e/σ_uts come from `material` or the `uts_mpa`/`endurance_mpa` overrides, and defines `s1000_fraction` and `endurance_cycles` in terms of S-N line endpoints. It leaves `cycles` only implicitly defined via 'survives `cycles`' and says nothing about `workspace`, keeping it short of a 5.

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?

Specific verb+resource: 'Rate fatigue life (S-N Basquin + Goodman mean-stress correction)', naming the exact method. It also states the governing criteria (infinite-life SF formula, finite-life log-log S-N extrapolation) so an agent knows precisely what this computes, distinguishing it from siblings like fracture_check or creep_flag.

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?

Gives domain guidance on when the defaults are appropriate — steel convention (0.9, 1e6) vs. non-ferrous alloys where no endurance knee exists and `endurance_cycles` must be set to the life σ_e was measured at. However, it never states when to pick this tool over sibling durability tools such as fracture_check, plate_check, or beam_buckling.

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