Skip to main content
Glama

Bolted Joint Check

bolted_joint_check
Read-only

Checks bolted joint preload and strength from bolt size or diameter, torque or preload, property class, and external load; returns stress, separation margin, and pass/fail.

Instructions

Rate a bolted joint (VDI 2230-lite). Geometry from bolt_dia_mm (+pitch_mm) OR a standard thread named via bolt_size ("M8"/"M8x1.0") that pulls dia/pitch and the standards-table tensile stress area; proof strength from the ISO 898-1 property_class ("8.8") when given. Preload from torque via T=KFd (pass torque_nm OR preload_n). Returns {preload_n, tensile_stress_area_mm2, bolt_stress_mpa, preload_pct_proof, bolt_stress_with_load_mpa, separation_load_n, separation_margin, pass, governing}. preload_target_pct is the fraction of proof strength the preload is judged against (0.75 default; 0.65 for a reused bolt, 0.90 for a critical permanent joint).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bolted_joint_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
k_factorNo
materialNoSteel-4140-QT
pitch_mmNo
bolt_sizeNo
preload_nNo
torque_nmNo
workspaceNoRun this call in this named workspace
bolt_dia_mmNo
property_classNo
external_load_nNo
preload_target_pctNo
proof_strength_mpaNo
joint_stiffness_ratioNo

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?

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description adds real value on top: the T=K*F*d preload relationship, the judgment basis (preload_target_pct against proof strength), and the exact output keys including pass and governing. It does not disclose failure modes or assumptions in the model beyond 'VDI 2230-lite', which keeps it from a 5.

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 core action, then geometry, preload, return keys, and the preload_target_pct rule in a logical order. Dense but nearly every clause carries information; the parenthetical standard-thread examples and the 0.75/0.65/0.90 guidance are the highest-value parts.

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 13-parameter, zero-required, no-output-schema tool, the description compensates well by enumerating the return object and the input alternatives. The remaining gap is that key defaults such as joint_stiffness_ratio, k_factor, and material are never described, so an agent must guess their effect on the rating.

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?

With only 8% schema description coverage the description must carry the load, and it explains roughly half the parameters: bolt_dia_mm, pitch_mm, bolt_size, property_class, torque_nm, preload_n, and preload_target_pct (including default and reuse/critical values). It leaves k_factor, material, external_load_n, joint_stiffness_ratio, proof_strength_mpa, and workspace unexplained, so several numeric parameters remain opaque to the agent.

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 ('Rate') and resource ('bolted joint') plus the governing standard (VDI 2230-lite), which cleanly separates it from sibling checks like spring_check, gear_rating, and weld_group. An agent can identify the tool's job 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 the two input paths — geometry via bolt_dia_mm (+pitch_mm) OR a standard thread via bolt_size — and the preload path via torque_nm OR preload_n, plus the property_class shortcut. It does not, however, say when to prefer this over adjacent checks such as suggest_loosening or fatigue_check, so it stops short of full when/when-not guidance.

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