Skip to main content
Glama

MIDAS CIVIL NX tools (MIDAS IT Europe)

Bridge Reshaper — change spans, skews, alignment and levels

bridge_reshape
Destructive

Changes the geometry of the bridge in the open model in place, with the Bridge Reshaper plugin's own engine (1.0.5): new span lengths (the deck is stretched - each span keeps its element count), a skew for each support, a new horizontal alignment (straight, segments, fitted points, LandXML/DXF) and new deck levels (flat, grades with parabolic vertical curves, one-way or crowned cross slope). crossMembers 'parallel' (default) moves nodes only - every element, node, load, group, stage and lane keeps its id; 'square' re-meshes the deck with cross members square to the girders running on to the skewed support lines (straight decks of beam girders only, not with new levels). Loads, structure groups, construction stages, lanes, tapered groups and links follow the deck; beam loads in global axes, plane loads and lane end skews are turned with it; piers and abutments follow their supports ('follow' the skew, or 'rigid' keep their shape). Previews by default: the changes, the issues and a plan drawing (grey = as it is, blue = proposed), with a planHash; nothing is written. With apply: true and confirmPlanHash it re-reads the model, refuses if anything changed since the preview, writes, reads every written node and element back, and records the run for bridge_reshape_undo. Lengths and chainages in the model's unit. Use bridge_reshape_read first. Runs as a background job on the website (poll job_status).

Input Schema

NameRequiredDescriptionDefault
axisNoSpans run along global X or Y. Default: X, or Y when no deck is found along X (the read says which it used).
applyNoWrite to CIVIL NX. Only after the user approved the preview (and saved a copy of the model).
skewsNoNew skew of every support in degrees from square, Abutment A first; null keeps one. Default: as modelled.
spansNoNew length of every span, Abutment A first (model unit). Default: as modelled.
layoutNoDeck in straight pieces only: straight (lay it straight) or turns at joints, piers or chainages, each with its angle in degrees (positive turns left).
levelsNoNew deck levels (default: as modelled). Each node keeps its depth below the deck surface; piers and abutments are stretched vertically to meet the deck (their lowest node stays).
pictureNoReturn a plan drawing (PNG) to look at.
skewAllNoInstead of skews: the same skew at every support.
supportsNoWhere the supports are, chosen instead of the ones found — when the plugin finds none (bearings it cannot read) or finds every construction-stage support defined. Each: ch = chainage along the deck from where its girders start (model unit), skew in degrees from square. At least the two ends. bridge_reshape_read reports the girders' extent and the supports it found.
alignmentNoA new horizontal alignment (default: as modelled - a curved deck keeps its curve). straight: a straight line through the deck start, at the deck's start heading or headingDeg (straightens a curved deck). segments: straights, arcs and clothoid transitions from the deck start, along the deck. points: a curve fitted to X,Y points (model coordinates unless keepCoordinates: false): spline through them, or a least-squares arc or polynomial. landxml / dxf: the file's text. The deck line that follows it is the centreline unless followLine names a girder/edge line (index from bridge_reshape_read).
deckGroupsNoStructure groups that ARE the deck, when the automatic choice is wrong. Default: found from the model.
crossMembersNoparallel
substructureNofollow: piers and abutments shear with their support's skew; rigid: they keep their shape and turn with it.follow
addToEverySpanNoInstead of spans: add this to every span.
confirmPlanHashNoplanHash from the approved preview; the write is refused if the plan differs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

With destructiveHint=true already set, the description adds crucial context: previews write nothing, apply requires a matching planHash, the model is re-read and refused if changed, written elements are read back, and the run is recorded for bridge_reshape_undo. It also notes the background job and job_status polling.

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?

The description is front-loaded with purpose and every clause is informative, but it is a dense, long block with many semicolon-separated details. For a 15-parameter mutation tool the length is justified, though bullets or shorter sentences would improve scanability.

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 destructive mutation tool with no output schema, the description covers the essential workflow: read first, preview default, confirm before writing, stale-plan refusal, undo recording, units, and background execution. An agent has enough to invoke it safely.

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 description coverage is already 93%, so the baseline is 3. The description adds meaningful consequences beyond the schema for key parameters, such as 'parallel' moving nodes only versus 'square' re-meshing the deck, 'follow' vs 'rigid' substructure behavior, and the apply/confirmPlanHash workflow.

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?

The description opens with a specific verb and resource: 'Changes the geometry of the bridge in the open model in place.' It enumerates the four main capabilities (spans, skews, alignment, levels) and distinguishes itself from bridge_reshape_read and bridge_reshape_undo.

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?

It explicitly says 'Use bridge_reshape_read first' and describes the two operating modes: preview by default versus 'With apply: true and confirmPlanHash'. It also states when 'square' cross members are valid and when they are not ('not with new levels').

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