Skip to main content
Glama

Elastica Deflection

elastica_deflection
Read-only

Calculate exact large-deflection cantilever tip slope and displacement, including axial draw-in and nonlinear-to-linear divergence, to validate nonlinear FEM results.

Instructions

Exact large-deflection cantilever tip — Bisshopp–Drucker elastica (NO solver) — the closed-form twin the *NLGEOM CalculiX solve is gated against. Section: width_mm+height_mm (solid rectangle, I = b·h³/12, load transverse to height_mm) or explicit i_mm4. E from youngs_gpa or a Materials-DB material. Load parameter α = P·L²/(E·I); the tip slope solves the elliptic-integral elastica. Linear theory δ/L = α/3 over-predicts the transverse tip and ignores the axial draw-in — the elastica captures both, and nonlinear_over_linear is the divergence the solve must reproduce. Valid for tip slope < ~80° (α ≲ 3.5); beyond that escalate to a follower-load fem_set_nonlinear_material solve.

Returns {alpha, tip_slope_deg, tip_disp_mm (transverse), tip_x_mm (axial projection), axial_drawin_mm, linear_tip_mm, nonlinear_over_linear, youngs_mpa, I_mm4, 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": {
      "load_n": "<load_n>",
      "length_mm": "<length_mm>"
    },
    "name": "elastica_deflection"
  }
}

Input Schema

NameRequiredDescriptionDefault
i_mm4No
load_nYes
materialNo
width_mmNo
height_mmNo
length_mmYes
workspaceNoRun this call in this named workspace
youngs_gpaNo

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

A5/5.0
Behavior5/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 materially beyond that: the calculation is closed-form with NO solver, the valid angle range is disclosed, the `nonlinear_over_linear` divergence metric is explained, and the escalation target is named. No side effects or hidden state are implied.

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-loads the purpose, then proceeds through section, elastic modulus source, α formula, linear-theory contrast, validity/escalation, and return fields in a compact engineering register. The density is justified by the low schema coverage and the lack of an output schema.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 supplies the return-field list (`alpha`, `tip_slope_deg`, `tip_disp_mm`, `axial_drawin_mm`, etc.) plus validity and escalation behavior an agent needs. Given the 8-parameter, low-coverage schema, it is complete enough to invoke and interpret correctly.

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 description coverage is only 13%, so the description must carry parameter meaning, and it does: `width_mm`/`height_mm` define a solid rectangle with I = b·h³/12 and load transverse to `height_mm`, `i_mm4` is an explicit alternative, E comes from `youngs_gpa` or a Materials-DB `material`, and α = P·L²/(E·I) ties `load_n` and `length_mm` to the solve. Only the generic `workspace` parameter goes unmentioned.

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?

Names a specific computation (exact large-deflection cantilever tip via the Bisshopp–Drucker elastica), the method (closed-form, no solver), and its role as the twin gated against the *NLGEOM CalculiX solve. The agent can distinguish it from FEA siblings because the description explicitly identifies `fem_set_nonlinear_material` as the escalation path.

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 bounds validity (tip slope < ~80°, α ≲ 3.5) and says to escalate to a follower-load `fem_set_nonlinear_material` solve beyond that range. It also contrasts linear theory to signal when the elastica is needed, so both when-to-use and when-not-to-use are present with a named 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