Skip to main content
Glama

MIDAS CIVIL NX tools (MIDAS IT Europe)

Stress distribution through a beam section (Stress Profile Generator)

stress_profile
Read-only

The Stress Profile Generator's profile for ONE beam element: from CIVIL NX's beam forces and the true section outline it calculates σx (or σx from N / My / Mz, τ from Vz / Vy, von Mises, principal, Tresca) over the section at the chosen positions and loads, and checks every profile against CIVIL NX's own published stresses (effective PSC sections are drawn through CIVIL NX's stress points; composite sections part by part from CIVIL NX's per-part results; envelopes give CIVIL NX's values at the stress points plus the governing member or static part as a profile). Returns per profile: status (ok/unchecked/points/refused) with reasons, forces, extremes and where they occur, CIVIL NX vs calculated at stress points 1–4, per-part σx for composites, and min/max across the section at each depth. With thermal it gives the EN 1991-1-5 temperature stresses instead, split into total, restraint, self-equilibrating, uniform and linear parts (Type 3 heating/cooling with 100 mm surfacing, a user ΔT profile, or CIVIL NX's own section temperature; restraint free, full, axial, rotation, or CIVIL NX's forces of a load). Optional csv gives the plugin's CSV export as a download link. Read-only.

Input Schema

NameRequiredDescriptionDefault
csvNoAlso return the plugin's CSV export of every profile (a download link).
unitNoStress unit of the results (internally kN/m²).MPa
loadsNoLoad case / combination / envelope names as stress_element_loads lists them; with stage, that stage's results (e.g. Summation, Dead Load).
stageNoConstruction stage: use its results (last step) instead of the final state.
resultNosx σx combined; sxN/sxMy/sxMz its parts; tVz/tVy shear; vm von Mises; s1/s2 principal; tmax; tresca.sx
thermalNoTemperature stresses instead of load results (EN 1991-1-5 §6.1.4).
elementIdYesThe beam element.
positionsNoPositions along the element: I-end, ¼, ½, ¾ span, J-end. Default ["2/4"].
depthLevelsNoLevels of the through-depth table (vertex levels are added); 0 leaves it out.
sectionPropertiesNoeffective = CIVIL NX's own stresses (as the plugin's default); gross = the plugin's calculation on the section as modelled, difference stated.effective

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 adds substantial behavior: verification against CIVIL NX stresses, per-profile statuses (ok/unchecked/points/refused), composite per-part results, envelope handling, and thermal decomposition. It does not cover error recovery beyond status codes, but transparency is strong.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single massive run-on sentence with nested parentheticals and semicolons. It is front-loaded with purpose, but the structure makes it difficult to parse despite the information being relevant.

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?

For a complex 10-parameter nested tool with no output schema, the description explains return values, statuses, composite handling, thermal variants, and CSV export. It provides enough operational context for an agent to invoke the tool correctly.

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 the 10 parameters and their enums. The description contextualizes the thermal and result options but mostly restates schema content rather than adding new syntax, defaults, or interaction rules beyond what is structured.

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?

Specific verb and resource: it calculates stress profiles for ONE beam element from CIVIL NX's beam forces and true section outline, with detailed scope. It lacks explicit sibling differentiation, e.g. from stress_element_loads or sls_stress_check, so it is clear but not fully routing-aware.

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?

No explicit when-to-use, when-not-to-use, or alternative routing. The use case is implied by 'profile for ONE beam element' and the thermal branch, but an agent must infer which sibling to choose.

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