Skip to main content
Glama
Sign In

Structomat

by com.structomat
OverviewDiscussionsAdmin

Check a standard steel connection (instant utilisation)

check_connection
Read-onlyIdempotent

Instant utilisation (demand/capacity) of a standard steel connection under the given member-end forces, from capacities precomputed with finite-element connection analysis to AISC 360-16 LRFD (S275 steel, grade 8.8 bolts, C30/37 concrete). Returns the utilisation, the governing component (and the governing plate, weld or bolt group) and warnings. Call without "template" to list the templates and sizes. Forces are member-end forces at the analysis node, i.e. at the centreline of the supporting column or main beam (as a frame analysis gives them), not at its face; the capacities already include the offset. Only for a joint where no other member frames in: if anything else connects at the node, the result does not apply (ask for a connection design instead). For a first idea of a connection; a design for construction needs a checked calculation.

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": {
      "other_members_at_node": "<other_members_at_node>"
    },
    "name": "check_connection"
  }
}

Input Schema

NameRequiredDescriptionDefault
N_kNNoMember-end force at the node, kN: the force the loaded member applies to the connection, in member axes (x away from the node). Positive = tension (pulls away from the node).
Vy_kNNoBase plate only: horizontal shear along the column flanges, kN.
Vz_kNNoBeams: vertical shear the beam applies to the connection, kN, positive UPWARDS (gravity shear is negative). Base plate: horizontal shear along the column web.
My_kNmNoMajor-axis moment at the node, kNm (moment templates only). Positive = top flange of the beam in tension (hogging).
membersNoSection of each member by role, e.g. {"column": "HEA300", "beam": "IPE330"}.
templateNoConnection template. Omit to list templates and sizes.
other_members_at_nodeYestrue if any other member (brace, second beam, etc.) connects at the same node.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / My_kNm / description
      Previous value: -"Major-axis bending moment, kNm (moment templates only)."New value: +"Major-axis moment at the node, kNm (moment templates only). Positive = top flange of the beam in tension (hogging)."
    • changedInput schema / properties / N_kN / description
      Previous value: -"Axial force at the loaded member end, kN (tension positive)."New value: +"Member-end force at the node, kN: the force the loaded member applies to the connection, in member axes (x away from the node). Positive = tension (pulls away from the node)."
    • changedInput schema / properties / Vy_kN / description
      Previous value: -"Shear Vy, kN (base plate only)."New value: +"Base plate only: horizontal shear along the column flanges, kN."
    • changedInput schema / properties / Vz_kN / description
      Previous value: -"Shear Vz (vertical shear of a beam), kN."New value: +"Beams: vertical shear the beam applies to the connection, kN, positive UPWARDS (gravity shear is negative). Base plate: horizontal shear along the column web."
  2. Changed1 schema field changed
    • changedInput schema / properties / template / enum
      Previous value: -[
-  "end_plate_moment",
-  "widened_end_plate_moment",
-  "fin_plate_column_web",
-  "beam_to_beam_end_plate",
-  "pinned_base_plate"
-]New value: +[
+  "flush_end_plate_moment",
+  "extended_end_plate_moment",
+  "fin_plate_column_web",
+  "beam_to_beam_end_plate",
+  "pinned_base_plate"
+]
  3. Added

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already cover safety (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds substantively: precomputed FE-based capacities, the design assumptions baked in (S275, grade 8.8, C30/37), the return payload, and the critical caveat that capacities already include the column-face offset. It also scopes the validity of results, which annotations cannot express.

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?

Well front-loaded: purpose and returns come first, caveats after. The force-location sentence is long and dense, but each clause carries necessary engineering meaning rather than filler.

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 still names what comes back (utilisation, governing component and the governing plate/weld/bolt group, warnings). Combined with the applicability limits and force conventions, an agent has everything needed to call it correctly and interpret the answer.

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?

Schema coverage is 100%, so the baseline is 3; the description earns an extra point by clarifying that forces are member-end forces at the analysis node centreline rather than at the column face, which changes how an agent maps frame-analysis output onto N_kN, Vz_kN and My_kNm. It also explains the omit-template behaviour, adding meaning beyond the enum list.

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 and resource ('Instant utilisation (demand/capacity) of a standard steel connection') plus the code basis (AISC 360-16 LRFD) and the return content (utilisation, governing component, warnings). An agent can tell this apart from siblings like get_connection or analyze_frame without opening the schema.

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 explicit when-to-use ('for a first idea of a connection'), when-not-to-use ('only for a joint where no other member frames in... ask for a connection design instead'), and a discovery path ('call without "template" to list the templates and sizes'). No alternative needs to be inferred.

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

All Structomat toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources