Skip to main content
Glama

Beam Buckling

beam_buckling
Read-only

Screen column buckling with closed-form Euler/Johnson equations to get critical stress, critical load, and safety factor; escalate to FEM for non-prismatic or eccentric cases.

Instructions

Exact column-buckling screen (Euler + Johnson, NO solver) — the closed-form twin the CalculiX fem_buckling eigen-solve is gated against (as beam_modal is to fem_modal). Section: width_mm+height_mm (solid rectangle, weak axis automatic), diameter_mm (round), or explicit area_mm2+i_min_mm4. E/σ_y from youngs_gpa/yield_mpa or a Materials-DB material. end_condition: 'pinned_pinned' | 'fixed_free' | 'fixed_pinned' | 'fixed_fixed' (theoretical K). Euler σ_cr=π²E/λ² above the transition slenderness √(2π²E/σ_y), Johnson parabola below (both exactly σ_y/2 at it). With load_n the safety factor P_cr/P is returned. Escalate to fem_buckling for non-prismatic / eccentric / built-up cases.

Returns {end_condition, k_factor, slenderness, transition_slenderness, governing, sigma_cr_mpa, p_cr_n, area_mm2, i_min_mm4, radius_gyration_mm, safety_factor, fidelity, band_pct, valid_range_ok, warnings, escalate_to}.

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": {
      "length_mm": "<length_mm>"
    },
    "name": "beam_buckling"
  }
}

Input Schema

NameRequiredDescriptionDefault
load_nNo
area_mm2No
materialNo
width_mmNo
height_mmNo
i_min_mm4No
length_mmYes
workspaceNoRun this call in this named workspace
yield_mpaNo
youngs_gpaNo
diameter_mmNo
end_conditionNopinned_pinned

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

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

Going well beyond the readOnlyHint/openWorldHint annotations, it discloses the governing physics regime switch (Euler above transition slenderness, Johnson parabola below, both σ_y/2 at transition), that no solver runs, and that fidelity/band_pct/warnings/valid_range_ok flags are emitted. It does not say what happens when valid_range_ok is false or how fidelity is graded, so not 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 identity and sibling relationship, then parameter guidance, then escalation advice — a sensible order. It is dense and uses shorthand ('weak axis automatic', 'λ²') that assumes domain fluency, but almost every clause carries distinct information.

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, the description correctly enumerates the return fields and their meaning (k_factor, transition_slenderness, governing, safety_factor, band_pct, escalate_to), which is essential here. Minor gaps remain around invalid-input behavior and the unexplained workspace parameter.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 8%, so the description carries the load, and it does: it defines three mutually exclusive section-specification routes (width+height, diameter, or area+i_min), how E and σ_y are sourced (youngs_gpa/yield_mpa vs. Materials-DB material), the four end_condition strings with their theoretical K, and load_n's role in producing the safety factor. The only uncovered parameter is the cross-cutting workspace.

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 ('Exact column-buckling screen (Euler + Johnson, NO solver)') and immediately positions it against a named sibling, fem_buckling, via the beam_modal/fem_modal analogy. An agent can distinguish it from the FEM eigen-solve tools without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly defines the boundary: use this for prismatic closed-form screening, 'escalate to fem_buckling for non-prismatic / eccentric / built-up cases.' It also implicitly covers when the closed-form is valid via the transition-slenderness explanation. No ambiguity about the alternative.

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