MIDAS CIVIL NX tools (MIDAS IT Europe)

Undo a thermal write or remove

bridge_thermal_undo

Destructive

Undoes the latest bridge_thermal_apply or bridge_thermal_remove run (or the run named): deletes the EC1T_ cases present now and puts back the EC1T_ cases and loads saved before that run, merged into each element's current loads so other cases are kept. Refused in a different model or after a unit change; needs force if EC1T_ loads or the geometry changed since. 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_undo"
  }
}

Input Schema

Name	Required	Description	Default
`apply`	No
`force`	No
`runId`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the destructiveHint annotation: it discloses exactly what is deleted (EC1T_ cases present now), what is restored and how (saved cases/loads merged into current loads so other cases are kept), the preconditions that cause refusal, and the force requirement. It also discloses that the default is a dry run ('Previews unless apply: true'), which is critical for a destructive mutation.

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

Conciseness5/5

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

Front-loaded with what gets undone and what happens on disk, followed by refusal conditions and the preview default. Three tight sentences, no filler, and each clause carries operational meaning.

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 destructive, zero-required-parameter mutation with no output schema, the description covers effect scope, merge behavior, preconditions, and dry-run default. Nothing essential for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must carry all three parameters, and it does: 'apply: true' for execution vs. preview, 'force' for when EC1T_ loads or geometry changed since, and runId as 'the run named' vs. the default latest run. This fully compensates for the empty 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?

Specific verb ('Undoes') plus the exact resources it targets ('the latest bridge_thermal_apply or bridge_thermal_remove run'), naming the sibling tools it reverses. An agent can distinguish this from bridge_thermal_apply/remove and from unrelated *_undo tools without opening any schema.

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?

States the triggering condition (undoing the latest apply/remove run, or a specific run by id) and the failure conditions ('Refused in a different model or after a unit change'). It does not explicitly say what to do instead when force is needed or when no reversible run exists, so it stops short of full when/when-not/alternatives guidance.

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?