Skip to main content
Glama

FSI Plate Deflection

fsi_plate_deflection
Read-only

Computes closed-form small-deflection tip or centre deflection for uniform-pressure-loaded thin plate strips, supporting cantilever and clamped-clamped cases to validate FSI simulations.

Instructions

Exact small-deflection tip/centre deflection of a uniform-pressure-loaded thin plate strip (NO solver) — the closed-form twin the coupled OpenFOAM→CalculiX FSI solve (fsi_pressure_plate_submit) is gated against. The wetted strip is width_mm×length_mm; the fluid pressure pressure_pa (Pa) acts normal to it, giving the line load q = pressure·width. Section is the solid rectangle I = width·thickness³/12 unless an explicit i_mm4 is given. E from youngs_gpa or a Materials-DB material. support='cantilever' (clamped one edge): δ_tip = q·L⁴/(8·E·I), root moment q·L²/2, reaction q·L; 'clamped- clamped': centre δ = q·L⁴/(384·E·I), reaction q·L/2 each. Valid while δ ≲ thickness (small-deflection); past that escalate to an NLGEOM follower-pressure ccx solve.

Returns {support, pressure_pa, line_load_n_per_mm, total_load_n, I_mm4, tip_disp_mm, root_moment_nmm, reaction_n, max_stress_mpa, youngs_mpa, slenderness, 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": {
      "pressure_pa": "<pressure_pa>",
      "length_mm": "<length_mm>",
      "width_mm": "<width_mm>",
      "thickness_mm": "<thickness_mm>"
    },
    "name": "fsi_plate_deflection"
  }
}

Input Schema

NameRequiredDescriptionDefault
i_mm4No
supportNocantilever
materialNo
width_mmYes
length_mmYes
workspaceNoRun this call in this named workspace
youngs_gpaNo
pressure_paYes
thickness_mmYes

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?

Annotations only declare readOnly/openWorld=false, so the description carries the real behavioral load and does so well: it discloses the closed-form assumptions, the two support cases with their formulas, and the validity band. Minor gaps remain — failure modes (e.g. unknown material name, missing E) and what `fidelity`/`band_pct`/`warnings` mean are not explained.

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 key differentiator (closed-form, no solver) and every formula serves the caller's need to trust the result. It is dense and formula-heavy, and the return-field list is a long comma run, but little is genuinely wasted text.

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 9-parameter physics tool with no output schema, the description is nearly complete: it enumerates the return keys, the units of the inputs, the valid range, and the escalation path. It falls short only on error behavior and on the meaning of the diagnostics fields (`fidelity`, `band_pct`, `warnings`, `escalate_to`).

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 11%, so the description must compensate and does: it maps `pressure_pa` + `width_mm` to line load q, `length_mm` to L, `thickness_mm` to the section modulus, explains `i_mm4` as an override, `youngs_gpa` vs `material` as alternate E sources, and gives the two concrete `support` values. This adds substantially more meaning than the bare schema titles.

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 precise verb+resource: exact small-deflection closed-form tip/centre deflection of a uniform-pressure-loaded plate strip, with no solver involved. It also distinguishes itself from the sibling `fsi_pressure_plate_submit` by naming it as the coupled FSI solve this closed-form result gates against.

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 use condition (valid while δ ≲ thickness, small-deflection regime) and an explicit exit condition (past that, escalate to an NLGEOM follower-pressure ccx solve). It also names the alternative solver tool the caller would otherwise use, so an agent can route between the two without inference.

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