Skip to main content
Glama

Check steel members to AISC 360-16 (demand / capacity)

check_steel_members
Read-onlyIdempotent

Preliminary strength check of steel members to AISC 360-16 LRFD under the forces you give: available strengths and the demand-to-capacity ratio D/C of each member, the governing limit state and every step with its clause. Covers compression (flexural, torsional and local buckling, E3/E4/E7), tension yielding (D2), bending about both axes with lateral-torsional and local buckling (F2, F3, F6, F7, F8; Cb given or from the moment diagram, 1.0 for cantilevers), shear (G2.1, G4, G5, G6) and the H1-1 interaction, for I-sections (IPE, HEA, HEB, or dimensions: rolled when a root radius r > 0 is given, welded when r = 0 or "built_up": true), rectangular and square hollow sections (RHS/SHS) and round hollow sections (CHS), HSS design wall thickness 0.93t (B4.2). Steel grades ASTM A992, A36, A572 Gr. 50, A500 Gr. C, A53 Gr. B, or Fy; EN S235-S355 (EN 10025, EN 10219 as S..H) are checked with the AISC equations by analogy, since AISC 360-16 approves ASTM materials (A3.1a). The forces are taken as given: they must include second-order effects, from the direct analysis method of Chapter C or, with K from a stability analysis, the effective length method (analyze_frame gives elastic second-order forces without notional loads or stiffness reduction, and its result already has a member check of every member); the effective lengths are yours. Not covered (reported): webs noncompact or slender in flexure for I-sections, torsion, net-section rupture, connections, seismic provisions, fire. Up to 50 members per call; nothing is stored.

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": {
      "members": "<members>"
    },
    "name": "check_steel_members"
  }
}

Input Schema

NameRequiredDescriptionDefault
membersYesMembers to check.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / members / items / properties / Cb / description
      Previous value: -"Lateral-torsional buckling modification factor (default 1.0, or from cb_moments_kNm)."New value: +"Lateral-torsional buckling modification factor (default 1.0, or from cb_moments_kNm; F1-1 limited to 3.0 by this tool). Use 1.0 for a cantilever with an unbraced free end (F1)."
    • changedInput schema / properties / members / items / properties / Lcz_m / description
      Previous value: -"Effective length for torsional buckling, m (default Lcy)."New value: +"Effective length for torsional buckling, m (default L, independent of Lcy)."
    • addedInput schema / properties / members / items / properties / cantilever
      Added value: +{
      +  "description": "true for a cantilever with an unbraced free end: Cb = 1.0 (F1).",
      +  "type": "boolean"
      +}
    • changedInput schema / properties / members / items / properties / section / description
      Previous value: -"A name: \"IPE 300\", \"HEA 200\", \"HEB 400\", \"SHS 100x100x5\", \"RHS 200x100x6\", \"CHS 139.7x5\"; or dimensions in mm: {\"shape\":\"I\",\"h\":..,\"b\":..,\"tw\":..,\"tf\":..,\"r\":..}, {\"shape\":\"RHS\",\"h\":..,\"b\":..,\"t\":..}, {\"shape\":\"CHS\",\"D\":..,\"t\":..}."New value: +"A name: \"IPE 300\", \"HEA 200\", \"HEB 400\", \"SHS 100x100x5\", \"RHS 200x100x6\", \"CHS 139.7x5\"; or dimensions in mm: {\"shape\":\"I\",\"h\":..,\"b\":..,\"tw\":..,\"tf\":..,\"r\":..} (r = 0 or \"built_up\": true = welded), {\"shape\":\"RHS\",\"h\":..,\"b\":..,\"t\":..}, {\"shape\":\"CHS\",\"D\":..,\"t\":..}."
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the description only needs to add constraints — and it does: 50-member cap, "nothing is stored", unit conventions (kN, m), HSS wall thickness 0.93t, rolled vs welded inferred from root radius, and EN grades checked by AISC equations by analogy. Minor gap: no statement about output formatting or how unavailable checks are surfaced beyond being "reported".

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 purpose and deliverables, and nearly every clause carries technical information (clause numbers, section families, material grades). It is a single dense run-on block, however, so the coverage list and caveats are harder to scan than they need to be.

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?

No output schema, yet the description states what comes back (strengths, D/C, governing limit state, steps with clauses) and covers input assumptions, limits, and exclusions. Nothing an agent needs in order to call this correctly with a single nested "members" array is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the per-field semantics are already documented; the description only adds cross-field meaning such as Cb being taken from the moment diagram or forced to 1.0 for cantilevers and the enlarged/unconservative scope of assumed forces. That is useful but does not go materially beyond the schema.

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?

Opens with a specific verb, resource and standard: "Preliminary strength check of steel members to AISC 360-16 LRFD", and names the outputs (available strength, D/C ratio, governing limit state, clause-by-clause steps). This lets an agent separate it from analyze_frame, which the description explicitly says already performs its own member check.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives explicit preconditions (forces must already include second-order effects from Chapter C or the effective length method, effective lengths are the caller's responsibility) and explicitly excludes/reports out-of-scope items (slender webs in flexure, torsion, net-section rupture, connections, seismic, fire). It stops short of naming a single preferred alternative for the cases it declines, but the boundary is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources