FERS — structural FEM

Check a steel beam (EN 1993-1-1)

check_beam

Read-only

Check a steel beam to EN 1993-1-1 (Eurocode 3). Builds the beam + a ULS load combination + an EC3 member check over one member, solves it, and returns the governing utilization (<= 1.0 = OK) with the per-rule breakdown: bending, shear, combined N+M, and lateral-torsional buckling, plus a short advice string, and deflection: the peak deflection under the unfactored (characteristic) load in mm, where it occurs (at_m) and span/deflection. The deflection includes shear deformation, and is reported, not checked against a limit. Requires a named library section: European (IPE/HEA/HEB/HEM/UPE/RHS/SHS/CHS), UK (UB/UC/PFC) or US (W/HP/HSS/Pipe). Accepts common parameter aliases (span/length for span_m, load_kN_per_m/uniform_load for udl). Set restrained=true if the compression flange is continuously laterally restrained (skips the LTB check). On this hosted server the solve does NOT run here: the tool validates the model, parks it and returns an open_url that solves it in the user's browser, where the results are shown. Tell the user to open the link; for results inside the chat they can install the local FERS MCP server. Units: m, kN, kN/m.

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": {
      "section": "<section>"
    },
    "name": "check_beam"
  }
}

Input Schema

Name	Required	Description
`udl`	No	Uniformly distributed load in kN/m, downward
`span`	No	Alias for span_m (beam span in metres)
`length`	No	Alias for span_m (beam span in metres)
`span_m`	No	Beam span in metres (required — or use alias `span`/`length`)
`section`	Yes	Library section name, e.g. 'IPE300', 'HEA200', 'UB 457x191x67', 'W10X22' (required). Carries the EC3 moduli.
`support`	No	'simply_supported' (default), 'cantilever', or 'fixed' (fixed–fixed)
`material`	No	steel_S235 (default), steel_S275, steel_S355 or steel_S460 (shorthand S235/S275/S355/S460 ok)
`point_load`	No	Point load in kN, downward
`restrained`	No	true if the compression flange is continuously laterally restrained (e.g. by decking or a slab) — the LTB (§6.3.2) check is then skipped. Default false.
`uls_factor`	No	ULS load factor applied to the load (default 1.35)
`uniform_load`	No	Alias for udl (uniformly distributed load in kN/m)
`load_kN_per_m`	No	Alias for udl (uniformly distributed load in kN/m)
`point_position`	No	Point-load position along the span, 0..1 (default mid-span; tip for a cantilever)
`laterally_restrained`	No	Alias for restrained

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 21, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only declare readOnly/openWorld/idempotent hints; the description adds substantial behavior: the hosted server does NOT solve, it validates, parks the model and returns an open_url for browser-side solving, and additionally discloses that deflection includes shear deformation and is reported rather than limit-checked, and that restrained=true skips the LTB rule.

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?

Dense but front-loaded: the check scope and return shape come first, then constraints, then the hosted-server caveat. A few clauses redundantly repeat schema content (alias list, restrained definition), but nothing is padding.

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 14 parameters and no output schema, the description carries the burden well: it enumerates the returned breakdown (bending, shear, N+M, LTB, advice, deflection with at_m and span/deflection), states the <=1.0 pass criterion, and explains the deferred-solve behavior an agent must relay to the user.

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 schema already documents aliases, defaults, and units for every parameter; the description largely restates them (alias list, restrained semantics, units: m, kN, kN/m). It adds no new semantics about how udl and point_load interact or how uls_factor applies to each, which would have been genuinely additive.

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 ('Check a steel beam to EN 1993-1-1 (Eurocode 3)') and scopes it as a one-shot pipeline over a single member: build beam + ULS combination + EC3 check, solve, return governing utilization. This is clearly distinguishable from siblings such as create_beam, add_unity_check, or solve_model, which do one piece at a time.

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 clear usage context: set restrained=true when the compression flange is continuously restrained (skips LTB), aliases are accepted, and results only appear via the returned open_url on this hosted server, with the local FERS MCP server as the alternative for in-chat results. It stops short of explicitly contrasting with the manual create_beam + add_load_combination + run_unity_checks path, so no true when-not/exclusion statement.

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

All FERS — structural FEM tools Inspect

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.