Skip to main content
Glama

Plastic Collapse

plastic_collapse
Read-only

Compute the exact plastic-hinge collapse load and moment for a solid rectangular beam in bending, including shape factor, yield and plastic margins, and elastic, partially plastic, or collapsed regime.

Instructions

Exact plastic-hinge collapse of a solid rectangular beam (NO solver) — the closed-form twin the perfectly-plastic CalculiX solve (fem_set_nonlinear_material) is gated against. The beam bends about the width_mm axis (depth = height_mm). σ_y from yield_mpa or a Materials-DB material. Elastic modulus S = b·h²/6, plastic modulus Z = b·h²/4, shape factor Z/S = 1.5; yield moment M_y = σ_y·S, fully-plastic moment M_p = σ_y·Z. support maps the collapse moment to a point load: 'cantilever' (M = P·L) or 'simply_supported' (central, M = P·L/4). With load_n the applied moment and its margins to M_y / M_p (and the regime: elastic / partially_plastic / collapsed) are returned. A perfectly-plastic FEM solve caps the surface stress at σ_y and loses equilibrium at M_p; linear theory climbs past both — that contrast is the gate. Escalate to fem_set_nonlinear_material for non-rectangular sections or partial-plasticity fields.

Returns {support, S_elastic_mm3, Z_plastic_mm3, shape_factor, yield_mpa, yield_moment_nmm, plastic_moment_nmm, yield_load_n, collapse_load_n, applied_moment_nmm, margin_to_yield, margin_to_collapse, regime, 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>",
      "width_mm": "<width_mm>",
      "height_mm": "<height_mm>"
    },
    "name": "plastic_collapse"
  }
}

Input Schema

NameRequiredDescriptionDefault
load_nNo
supportNocantilever
materialNo
width_mmYes
height_mmYes
length_mmYes
workspaceNoRun this call in this named workspace
yield_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/5.0
Behavior4/5

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

Annotations declare readOnlyHint=true and openWorldHint=false, so safety is already covered. The description adds real value beyond that: it discloses the contrast behavior (linear theory climbs past M_y/M_p, FEM loses equilibrium at M_p) and enumerates diagnostic outputs like fidelity, band_pct, valid_range_ok, and warnings. The meaning of those diagnostic fields isn't elaborated, keeping it shy of 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 definition, then formulas, then the return contract. Dense but every clause — formulas, support mapping, escalation — carries information an agent needs; the parenthetical formula clutter is the only mild cost.

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?

Despite no output schema, the description enumerates the full return object, covering support, moduli, moments, margins, regime, and diagnostics. With annotations handling safety and the return contract spelled out, the definition is nearly complete; only the diagnostic field semantics (band_pct, valid_range_ok) are left implicit.

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 13%, so the description must carry the load, and it does: it pins the bending axis (`width_mm` axis, depth = `height_mm`), explains σ_y sourcing from `yield_mpa` or a Materials-DB `material`, and maps `support` values ('cantilever' M=P·L, 'simply_supported' M=P·L/4). `length_mm` and `workspace` are left to inference, but the domain-critical parameters are well covered.

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 artifact: exact closed-form plastic-hinge collapse of a solid rectangular beam with no solver. It also distinguishes itself from its sibling by naming `fem_set_nonlinear_material` as the gated perfectly-plastic solve, so an agent can tell the two apart immediately.

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?

Gives an explicit escalation rule — use `fem_set_nonlinear_material` for non-rectangular sections or partial-plasticity fields — and frames the tool as the analytical twin for rectangular sections. The when-not condition is stated outright, not inferred.

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