Skip to main content
Glama

Plate Check

plate_check
Read-only

Calculate handbook bending stress and deflection for uniformly loaded flat rectangular or circular plates to screen whether FEM is needed; flags thin-plate and small-deflection limits.

Instructions

Handbook bending of a uniformly loaded flat plate (NO solver) — the "do I need FEM at all?" screen. shape: 'rectangular' (a_mm × b_mm, short side drives; Roark/Timoshenko ν=0.3 coefficients σ=β·q·b²/t², δ=α·q·b⁴/(E·t³), interpolated in a/b) | 'circular' (diameter_mm; exact closed forms). support: 'simply_supported' | 'clamped' (all edges). E from youngs_gpa or a Materials-DB material (which also supplies yield for yield_safety_factor). Exact within thin-plate theory, and the limits are returned as flags (thin_plate_ok: span/t ≥ 10; small_deflection_ok: δ ≤ t/2) — a tripped flag means escalate to the CCX fem_* pipeline (escalate_to='fem_run').

Returns {shape, support, aspect_ratio, beta, alpha, sigma_max_mpa, deflection_max_mm, yield_safety_factor, thin_plate_ok, small_deflection_ok, 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": {
      "shape": "<shape>",
      "thickness_mm": "<thickness_mm>",
      "pressure_kpa": "<pressure_kpa>"
    },
    "name": "plate_check"
  }
}

Input Schema

NameRequiredDescriptionDefault
a_mmNo
b_mmNo
shapeYes
poissonNo
supportNosimply_supported
materialNo
workspaceNoRun this call in this named workspace
youngs_gpaNo
diameter_mmNo
pressure_kpaYes
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.7/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses the solution method (Roark/Timoshenko coefficients, ν=0.3, interpolation in a/b), that circular cases use exact closed forms, that results are exact only within thin-plate theory, and that validity limits surface as flags rather than exceptions.

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 purpose and the alternate-case routing before the formulas, and every clause carries information. It is dense with parenthetical formulas and enum lists, which makes it heavier to scan than necessary, but nothing is padding.

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 enumerates the returned fields and explains the important ones (validity flags, escalate_to, yield_safety_factor). A few returned fields such as fidelity and band_pct are listed without saying what they mean, which is a small residual gap for an 11-parameter analysis tool.

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?

Critical because schema coverage is only 9%: the description supplies the 'shape' values (rectangular vs circular), which dimensions each uses (a_mm × b_mm with short side driving; diameter_mm for circular), the 'support' options, and the youngs_gpa vs material precedence including that material also supplies yield. It leaves thickness_mm, pressure_kpa, poisson and workspace undocumented, but the names are largely self-evident.

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+resource: handbook (closed-form) bending check of a uniformly loaded flat plate, explicitly 'NO solver'. It self-describes as the 'do I need FEM at all?' screen, which cleanly separates it from the many fem_* siblings in the catalog.

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 decision rule: use this as the pre-FEM screen, and if a validity flag trips (thin_plate_ok or small_deflection_ok), escalate via escalate_to='fem_run' to the CCX fem_* pipeline. Both the when and the when-to-hand-off are named, along with 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