Skip to main content
Glama

Bearing Life

bearing_life
Read-only

Calculate ISO 281 basic rating life L10 in revolutions and hours from equivalent load, speed, and dynamic rating, or pull dynamic load from a bearing designation and check against target hours.

Instructions

Basic rating life L10 (ISO 281): L10=(C/P)^p rev (p=3 ball, 10/3 roller), L10h=L10*1e6/(60n). Supply the dynamic rating C as dynamic_load_c_n, or pull it from the deep-groove ball catalog by designation (e.g. "6205" -> C=14.0 kN, also reporting bore/OD/width, C0 and static safety factor). Returns {l10_million_rev, l10_hours, load_ratio, dynamic_load_c_n, exponent, pass, ...} (pass vs target_hours when given).

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": {
      "equivalent_load_p_n": "<equivalent_load_p_n>",
      "speed_rpm": "<speed_rpm>"
    },
    "name": "bearing_life"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindNoball
speed_rpmYes
workspaceNoRun this call in this named workspace
designationNo
target_hoursNo
dynamic_load_c_nNo
equivalent_load_p_nYes

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

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

Beyond the readOnly/openWorld annotations, it discloses the side computation when a designation is used (bore/OD/width, C0, static safety factor) and the pass/fail comparison against target_hours. That is useful non-obvious behavior; minor gaps remain on units and failure modes.

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 governing equations and the C-input options, then the return fields. Dense but every clause carries engineering meaning; the trailing return-key enumeration is the least efficient part.

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?

With 7 parameters, 14% schema description coverage and no output schema, the description compensates by naming the key return keys and the catalog fallback behavior. What is missing (workspace semantics, units for P, valid kind values) is modest for a deterministic calculator.

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 14%, so the description carries the burden and mostly does: it ties C to dynamic_load_c_n, P to equivalent_load_p_n, n to speed_rpm, and explains kind via the exponent rule (p=3 ball, 10/3 roller). The workspace parameter and explicit unit conventions go unmentioned.

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?

States a specific verb and resource: computes ISO 281 basic rating life L10, with the governing formulas shown inline. It is clearly distinct from siblings like add_bearing (geometry) and catalog_search (lookup), and an agent can tell what it produces without opening the schema.

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?

Explicitly describes two input paths — supply C directly as dynamic_load_c_n, or resolve it from the deep-groove ball catalog by designation — which is real routing guidance. It does not state when to prefer this over siblings such as catalog_search or a full bearing rating, but the usage context is clear enough for a calculation tool.

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