Skip to main content
Glama

MIDAS CIVIL NX tools (MIDAS IT Europe)

Write bridge temperature loads (Bridge Thermal Loads)

bridge_thermal_apply

Calculates the temperature actions for the deck and writes them with the Bridge Thermal Loads plugin's writer: EC1T_Uniform_Exp/_Con (type T, element or system temperature), EC1T_Diff_Heat/Cool (type TPG: beam section temperature bands, or a linear gradient for Approach 1 and plates), and optionally EC1T_Bearing* and EC1T_Comb_Max/_Min (USER). Temperatures are converted to the model's unit; the model is re-checked before writing, an undo record is kept before the first change, and every row is read back. Previews unless apply: true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "bridge_thermal_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
T0NoInitial (restraint) temperature, °C. Default: the code's value where it gives one.
codeNoEN 1991-1-5 with the UK NA (default) or the CEN values, CS 454, BS 5400-2:2006 or the legacy BS 5400-2:1978.EN1991-1-5_2003_UKNA
siteNoFor the uniform component (and bearing / combined cases). Tmin / Tmax are the shade air temperatures read from the code's maps by the user (the maps are not built in), °C.
applyNo
groupNoStructure group holding the deck elements.
loadsNoLoad types to generate (each gives two cases). Default: uniform and difference.
methodNoTemperature difference: approach2 = non-linear profile (code profiles), approach1 = linear. Default: the code's (the CEN text leaves it to the annex — then it must be given).
suffixNoWrite a named set: every case name gets this suffix (letters, digits, _ or -, at most 12), e.g. _2.
materialNoBand material: element (default, the model's E and α) or input (the code's α with E given here, in the model's force/length² units).
overwriteNoReplace EC1T_ cases of the same names already in the model. Only with the user's agreement.
procedureNoComposite decks under EN: normal or simplified procedure.normal
surfacingNo
elementIdsNo
modularRatioNoEs/Ec, needed for combined cases on composite sections (LR 765 effective temperature).
simultaneityNoReport the simultaneity combinations (ω factors).
useSelectionNoUse the elements selected in CIVIL NX (when neither group nor elementIds is given).
trussReductionNoSteel truss / plate girder reduction where the code gives one.
confirmPlanHashNo
sectionOverridesNoCorrections to the sections bridge_thermal_read reports (by key or name).
wholeModelUniformNoWrite the uniform component as a system temperature on the whole model (all sections must be one deck type).
elementDifferencesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior5/5

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

Adds real behavioral context beyond the annotations: unit conversion to the model's units, a re-check of the model before writing, an undo record kept before the first change, and every written row read back. The preview-by-default/apply gate is exactly the kind of safety detail annotations alone (destructiveHint=false) cannot convey.

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?

Two dense sentences, front-loaded with what gets written before the safety/undo/apply behavior. Slightly heavy on case-name enumeration, but every clause carries information an agent needs.

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 21-parameter write tool with no output schema, the description covers the mutation lifecycle (preview, hash/confirm implied, undo, read-back) well. The main gap is the confirmPlanHash round-trip: an agent reading only this description would not know it must pass the hash from a preview to apply safely.

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 coverage is 76% and most parameters already carry descriptions, so baseline is 3. The description adds case-naming semantics (what EC1T_* names each option produces) but leaves notable parameters such as confirmPlanHash, group/elementIds precedence and useSelection unexplained in the prose.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a precise verb+resource (calculates and writes deck temperature actions via the Bridge Thermal Loads writer) and enumerates the exact case families produced (EC1T_Uniform_*, EC1T_Diff_*, bearing, combined). It is clearly distinguishable from bridge_thermal_calc and bridge_thermal_read in substance, though it never names those siblings explicitly.

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

Usage Guidelines3/5

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

The one explicit usage rule is strong – 'Previews unless apply: true' – plus 'overwrite ... Only with the user's agreement'. But there is no guidance on when to use this instead of bridge_thermal_calc/bridge_thermal_read, or on what to do when the code leaves method unspecified (it only says 'then it must be given').

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