MIDAS CIVIL NX tools (MIDAS IT Europe)

Save the model

civil_save_model

Saves the open CIVIL NX model: over its own file (doc/SAVE), or as a new .mcb file when path is given (doc/SAVEAS; a file of that name is overwritten). A model built from scratch must be saved once before it can be analysed. 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": "civil_save_model"
  }
}

Input Schema

Name	Required	Description	Default
`path`	No	Full Windows path ending in .mcb, e.g. C:\Models\Bridge.mcb. Omit to save over the model's own file.
`apply`	No

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A4.6/5.0

Behavior4/5

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

Goes beyond the annotations by disclosing the overwrite risk on the target path and the dry-run-by-default behavior tied to apply. It does not say whether the save operation is reversible or what the tool returns on a preview, so it is strong but not exhaustive given annotations already cover readOnly/openWorld hints.

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?

Three compact sentences with zero filler, front-loaded with the primary action and immediately followed by mode distinction, prerequisite, and the dry-run caveat. Every clause carries operational information.

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 two-parameter mutation tool with no output schema, the description supplies modes, prerequisites, and the preview default, which is nearly everything needed to call it correctly. A brief note on the expected confirmation/return of a preview versus a real save would close the remaining gap.

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 coverage is 50%: `path` is documented in the schema, but `apply` has no description there, and the description compensates by explaining that its absence means a preview rather than a real save. It also adds the overwrite consequence for `path`, which the schema does not state.

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?

Names a specific verb and resource ('Saves the open CIVIL NX model') and disambiguates the two modes it supports: save-over (doc/SAVE) versus save-as to a .mcb path (doc/SAVEAS). No sibling tool in the list performs a save, so the agent can identify this operation unambiguously.

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?

States selection logic for the two modes (omit path = overwrite own file; supply path = new .mcb), gives a prerequisite ('a model built from scratch must be saved once before it can be analysed'), and discloses the preview gate ('Previews unless apply: true'). That covers when to call it and how to configure it.

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?