Skip to main content
Glama

Gear Rating

gear_rating
Read-only

Calculate spur-gear tooth bending stress and safety factor with the Lewis equation from tangential force or power and speed, using an optional allowable stress override for first-order design screening.

Instructions

Rate spur-gear tooth bending (Lewis): sigma=Ft/(bmY). Pass tangential_force_n, or power_w + pinion_speed_rpm. Returns {tangential_force_n, pitch_dia_mm, pitch_line_velocity_m_s, lewis_form_factor, bending_stress_mpa, allowable_bending_mpa, bending_sf, pass}. First-order screen, not full AGMA. The allowable defaults to the material's fatigue endurance (else 0.3·UTS); allowable_bending_mpa overrides it with an AGMA/spec number.

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": {
      "module_mm": "<module_mm>",
      "teeth": "<teeth>",
      "face_width_mm": "<face_width_mm>"
    },
    "name": "gear_rating"
  }
}

Input Schema

NameRequiredDescriptionDefault
teethYes
power_wNo
materialNoSteel-4140-QT
module_mmYes
workspaceNoRun this call in this named workspace
face_width_mmYes
pinion_speed_rpmNo
lewis_form_factorNo
tangential_force_nNo
allowable_bending_mpaNo

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

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

Annotations declare read-only/non-open-world, and the description adds real behavior beyond that: the allowable stress default chain (material fatigue endurance, else 0.3·UTS) and the override rule for allowable_bending_mpa. It also discloses the accuracy tier of the calculation, which is the main risk an agent needs to know about.

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?

Front-loaded with the formula, then input options, then return keys, then the accuracy caveat. Every sentence carries distinct information with no restatement of the name or title.

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 no output schema, listing the returned keys is a valuable addition, and the model limitations are stated. Gaps remain for a 10-parameter tool: the meaning of lewis_form_factor as a possible override of the computed Y, the teeth parameter, and the workspace parameter are left unaddressed.

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 description coverage is only 10%, so the description must carry the load; it explains the force-input alternatives, the material-driven default, and the allowable override, and the formula implies the roles of module and face width. But teeth, lewis_form_factor, workspace, and the material string format are never mentioned, so several of the ten parameters remain unexplained.

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, resource, and method: 'Rate spur-gear tooth bending (Lewis)' with the governing equation. This clearly separates it from adjacent screening tools such as wear_estimate, fatigue_check, or hertz_contact.

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?

It tells the caller which input paths are acceptable ('tangential_force_n, or power_w + pinion_speed_rpm') and gives a scope limit ('first-order screen, not full AGMA'), which is useful when-not guidance. However, no sibling tools are named and no explicit conditions are given for choosing among them.

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