Skip to main content
Glama

Spring Check

spring_check
Read-only

Rates a helical compression spring and checks Wahl-corrected shear stress, spring index, buckling, and safety factor; pass force or deflection to get pass/fail.

Instructions

Rate a helical compression spring (Wahl). rate k=G d^4/(8 D^3 Na); corrected shear tau=Kw 8FD/(pi d^3). Pass force_n OR deflection_mm. Returns {spring_index, wahl_factor, rate_n_mm, force_n, deflection_mm, shear_stress_mpa, slenderness, buckling_flag, allowable_shear_mpa, shear_sf, pass}.

G and the allowable come from material unless overridden. shear_modulus_mpa sets G directly; allowable_shear_mpa replaces the 0.45·UTS estimate, which falls back to 700 MPa (spring steel) for a material carrying no UTS — pass it explicitly for anything else, since shear_sf and pass scale with it.

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": {
      "wire_dia_mm": "<wire_dia_mm>",
      "coil_mean_dia_mm": "<coil_mean_dia_mm>",
      "active_coils": "<active_coils>"
    },
    "name": "spring_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
force_nNo
materialNoSteel-1045
workspaceNoRun this call in this named workspace
wire_dia_mmYes
active_coilsYes
deflection_mmNo
free_length_mmNo
coil_mean_dia_mmYes
shear_modulus_mpaNo
allowable_shear_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

A3.9/5.0
Behavior4/5

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

With readOnlyHint=true already covering the safety profile, the description adds substantial behavior: formulas used, output keys, material-derived defaults, explicit overrides, and the 700 MPa fallback when material UTS is absent. It also warns that shear_sf and pass scale with allowable_shear_mpa. Remaining gaps are assumptions and exact pass criteria.

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?

The description is front-loaded with the purpose and formulas, then covers usage and override behavior efficiently. It is dense but technically appropriate, with little wasted text. Slightly tighter formatting around the return fields and override notes would improve readability.

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?

For a complex engineering check with no output schema, the description is fairly complete: it lists return fields, states the input alternative for force versus deflection, and explains material fallback and overrides. It still omits output field meanings, validity assumptions, and the role of free_length_mm, which keeps it from being fully complete.

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 compensate. It meaningfully explains force_n/deflection_mm, material, shear_modulus_mpa, and allowable_shear_mpa, and the formulas implicitly map d, D, and Na to the required geometry parameters. However, free_length_mm is never explained despite its likely role in slenderness/buckling, and workspace is left to 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?

The description states a specific verb and resource: 'Rate a helical compression spring (Wahl).' It immediately includes the governing rate and shear formulas, making the analysis purpose unambiguous. It does not explicitly contrast itself with siblings such as add_spring, so it falls short of a 5.

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?

Usage is clearly constrained by 'Pass force_n OR deflection_mm' and by the statement that material-derived G and allowable apply unless overridden. It also gives important override guidance for shear_modulus_mpa and allowable_shear_mpa. It does not name alternatives or when-not-to-use cases, so not a 5.

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