MIDAS CIVIL NX tools (MIDAS IT Europe)

Bridge thermal actions (EN 1991-1-5 / CS 454 / BS 5400-2)

bridge_thermal_calc

Read-only

Calculates bridge temperature actions with the Bridge Thermal Loads plugin's own engine: shade air and effective bridge temperatures, the uniform ranges ΔT_N,con / ΔT_N,exp (and bearing ranges), the vertical temperature difference (linear Approach 1 or the non-linear code profile, as depth/temperature points), CS 454 / BS 5400 combined X − Y values, and the simultaneity combinations, each with its clause. Codes: EN 1991-1-5 + UK NA (default) or CEN, CS 454, BS 5400-2:2006 / 1978. Needs no model.

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_calc"
  }
}

Input Schema

Name	Required	Description	Default
`D`	No
`h`	No
`T0`	No	Initial (restraint) temperature, °C. Default: the code's value where it gives one.
`code`	No	EN 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
`kind`	No	Deck type: steel_box, steel_plate (truss or plate girders), composite (concrete deck on steel girders), concrete_slab, concrete_beam, concrete_box.
`site`	No	For 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.
`loads`	No	Load types to generate (each gives two cases). Default: uniform and difference.
`method`	No	Temperature 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).
`sections`	No	Deck sections. For one section the shorthand kind / h / D may be used instead.
`procedure`	No	Composite decks under EN: normal or simplified procedure.	normal
`surfacing`	No
`modularRatio`	No	Es/Ec, needed for combined cases on composite sections (LR 765 effective temperature).
`simultaneity`	No	Report the simultaneity combinations (ω factors).
`trussReduction`	No	Steel truss / plate girder reduction where the code gives one.
`elementDifferences`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description reinforces the safe, model-free nature while adding behavioral context: results are reported 'each with its clause', the code's defaults are applied where a value is absent, and CEN may require the method to be supplied. It stops short of saying anything about cost, limits, or error behaviour.

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 verb and the full output inventory, then the code options, then the model-free constraint. Dense but every clause carries information; the single long sentence is heavy but not padded.

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 15-parameter, zero-required, deeply nested calculation tool with no output schema, the description does the important work: it enumerates the outputs an agent will receive and states the engine and code basis. Remaining gaps — how sections relate to the shorthand, when combined vs uniform/difference should be requested — are partially covered by the schema itself.

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 73%, so the schema already carries most parameter meaning, and the description largely restates it (code list, no built-in maps, clause reporting). It adds only marginal semantics beyond the schema, e.g. that simultaneity yields ω factors and that combined replaces uniform + difference, but the deeper interactions (sections vs the kind/h/D shorthand, modularRatio for composite combined cases) are left to 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?

States a specific verb and resource ('Calculates bridge temperature actions') and enumerates exactly which quantities are produced (shade air temperature, ΔT_N,con/exp, bearing ranges, vertical temperature difference, CS 454 X−Y, simultaneity combinations). The phrase 'with the Bridge Thermal Loads plugin's own engine ... Needs no model' distinguishes it from the sibling apply/read/remove tools of the same family.

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?

'Needs no model' implicitly signals this is a standalone calculation rather than the model-side bridge_thermal_apply, and the code list clarifies which design code to pick. However, no sibling is named and no explicit when-to-use / when-not-to-use rule is given for choosing between this, bridge_thermal_apply and bridge_thermal_read.

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

All MIDAS CIVIL NX tools (MIDAS IT Europe) 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.

Resources

Need Help?