Skip to main content
Glama

Laminate Properties

laminate_properties
Read-only

Calculate effective stiffness, thermal curvature, and first-ply yield margins for multilayer composite stacks with closed-form screening—no FEM solver required.

Instructions

Effective stiffness, thermal warp, and first-ply failure of a bonded multi-layer composite stack (NO solver) — the closed-form screening twin a layered multi-material CalculiX fem_run static solve is gated against (e.g. 1 metal layer + 1 plastic layer, or any [(material, thickness), …]).

layers is the stack bottom→top; each entry is a mapping with a thickness (mm) and either a corpus material name or explicit E/youngs_mpa/ youngs_gpa (+ optional nu/poisson, yield_mpa, cte/cte_per_k, density_kg_m3, thermal_conductivity_w_mk); explicit values override the card. width_mm scales EI / first-ply. Optional delta_T (K) gives the bimetal thermal curvature; force_n (in-plane, total across width) and/or moment_nmm (about the neutral axis) give the first-ply margin.

Computes the in-plane modulus (Voigt rule-of-mixtures parallel, Reuss series through-thickness); the transformed-section neutral axis, EI_eff, and flexural modulus E_flex = 12·EI/(b·h³); the CLT A/B/D matrices per unit width (B ≠ 0 ⇒ bending–extension coupling / warp warning); mass-averaged ρ, stiffness-weighted in-plane CTE, series/parallel thermal conductivity; the transformed-section bimetal curvature (= Timoshenko's two-layer formula exactly, also reported); and per-layer extreme-fibre stress → margin to yield → governing layer + load to first yield. A single-material stack reduces to that material's E / EI; a symmetric stack gives B = 0; ΔT = 0 or zero CTE-mismatch gives zero curl. Escalate to a layered fem_run solve for thick stacks, anticlastic curvature, free-edge interlaminar stress, or non-isotropic plies.

Returns {n_layers, width_mm, total_thickness_mm, layers, E_inplane_mpa, E_through_mpa, neutral_axis_mm, EI_eff_nmm2, E_flex_mpa, A_matrix, B_matrix, D_matrix, coupling_ratio, asymmetric, rho_eff_kg_m3, cte_eff_per_k, k_through_w_mk, k_inplane_w_mk, delta_T, thermal_curvature_per_mm, radius_of_curvature_mm, timoshenko_curvature_per_mm, applied_force_n, applied_moment_nmm, kappa_applied_per_mm, axial_strain, layer_stresses, first_ply, 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": {
      "layers": "<layers>"
    },
    "name": "laminate_properties"
  }
}

Input Schema

NameRequiredDescriptionDefault
layersYes
delta_TNo
force_nNo
width_mmNo
workspaceNoRun this call in this named workspace
moment_nmmNo

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.9/5.0
Behavior5/5

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

Annotations already mark the tool read-only and closed-world, and the description adds substantial context beyond that: it is a closed-form, no-solver computation with fidelity/band reporting, validity-range flags, warnings, and an `escalate_to` field. It also describes what physical effects are captured and when the model stops being appropriate.

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 and every paragraph contributes useful technical information, but it is dense and includes a very long return-field enumeration. That density is largely justified by the complex engineering domain and the absence of an output schema, though some readers may find it heavy.

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?

For a complex 6-parameter physics tool with no output schema and low schema coverage, the description covers input structure, physical assumptions, computed outputs, validity limits, warnings, and escalation conditions. An agent has enough information to invoke the tool correctly and interpret its limitations.

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 17%, but the description fully compensates: it defines `layers` as bottom-to-top mappings with `thickness` plus either a corpus `material` name or explicit `E`/`youngs_*` and optional `nu`, `yield_mpa`, `cte`, `density_kg_m3`, and `thermal_conductivity_w_mk`. It also explains `width_mm`, `delta_T`, `force_n`, and `moment_nmm` in physical terms.

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?

The first sentence states a specific verb+resource: effective stiffness, thermal warp, and first-ply failure of a bonded multi-layer composite stack. It also distinguishes itself from `fem_run` as a closed-form screening twin, so an agent can tell exactly what this tool does versus a solver.

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?

The description explains this is the screening counterpart to a layered `fem_run` solve and explicitly says to escalate to `fem_run` for thick stacks, anticlastic curvature, free-edge interlaminar stress, or non-isotropic plies. That gives clear when-to-use and when-not-to-use 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