MIDAS CIVIL NX tools (MIDAS IT Europe)

CS 455 calculation sheet (Excel)

cs455_export_calc_sheet

Read-only

The report. Assesses one element end exactly as cs455_assess and writes the plugin's reference-format calculation sheet (.xlsx: A4 pages, title block, geometry, materials, reinforcement, section properties, sagging/hogging bending, shear and torsion with live formulas and charts, summary of results, and a Summary sheet with demand, resistance and ratio per check). Returns a download link. Use the same rebar/links that cs455_describe_section confirmed against the user's drawing. Read-only on the model.

Input Schema

Name	Required	Description
`fy`	No	Reinforcement yield strength, MPa (default 500).
`end`	No
`fcu`	No	Concrete cube strength, MPa (default: from the model's EN grade C../.. — its cube value).
`cases`	No	Load cases / combinations by name (default: every load combination the model has).
`image`	No	cs455_describe_section only: return the drawing of the section with its bars (default true).
`links`	No	Links (omit for concrete-only shear, cl 5.6). Used by shear and by torsion.
`rebar`	Yes	The bar schedule, as the plugin's Reinforcement tab: cover (mm to the bar face, default 50), gap (mm between layers, default max(25, Ø)), rows [{face: bottom\|top\|side\|depth, layer (any whole number, 1 = outermost), count ('8' bars or '@150' spacing), dia (mm, or '1.128in', or '#9'), depth (mm below top, face 'depth' only), span ('±430:900' width limits), from/to/which (side bars)}], coords {datum: bc\|bl\|tc, text: 'y z dia' per line, mm}.
`shear`	No	Run the shear check (default true).
`report`	No
`element`	Yes
`maxRows`	No	Stop above this many force rows (default 1000).
`torsion`	No	Torsion check, CS 455 cl 5.17–5.27, on rows that carry a torque (default true, as in the plugin).
`location`	No
`stations`	No	Element ends to assess (default: the section's first element, both ends, midspan). Location 'support' removes the shear enhancement near supports.
`axialSign`	No	Positive MIDAS axial is tension (-1, default) or compression (1).
`sectionId`	Yes	The CIVIL NX section id (a beam section).
`momentSign`	No	Positive MIDAS My is sagging (1, default) or hogging (-1).
`restrained`	No	Compression bars are restrained by links (cl 5.3.1). Default false: compression bars get no compressive strength (cl 5.3.2(1)), conservative.
`concreteModel`	No	Figure 3.4.1 curve (default) or the constant 0.6 fcu/γmc block of cl 5.1(3).
`concreteParts`	No	Composite sections: { part id: f_cu } where a part's grade differs (describe lists the parts).
`tensionOrigin`	No
`classification`	No	RC only in these tools.
`drawingReference`	No
`secondaryActions`	No	Vy / T / Mz: assess N–My–Vz and list them (default), or refuse rows where they are non-zero.
`confirmDimensions`	No	Only after the user has compared the drawn section with the drawing: needed when CIVIL NX published no properties to check the outline against.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 26, 2026

TDQS

A4.1/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 useful behavior beyond that: it writes an .xlsx workbook, includes live formulas/charts, returns a download link, and is read-only on the model. It does not contradict the annotations and adds substantial output-side context.

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 dense but well targeted, listing the workbook contents and return behavior without repeating the schema. 'The report.' is slightly vague as an opener, but the rest is front-loaded and earns its place for a complex export tool.

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 25-parameter export tool with no output schema, the description explains the generated workbook's contents and that it returns a download link, plus the key prerequisite about rebar/links confirmed by cs455_describe_section. It is largely complete, though it could say more about file handling or failure behavior.

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 coverage is 76%, so the schema already documents most parameters in detail, including many nested rebar and links fields. The description adds contextual guidance about reusing confirmed rebar/links, but it does not explain the many optional parameters or their interactions beyond what the schema provides, making 3 the appropriate baseline.

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 states a specific action and output: assess one element end exactly as cs455_assess and write the plugin's reference-format .xlsx calculation sheet, returning a download link. It clearly differentiates this export/report tool from the assessment sibling by naming cs455_assess and detailing the Excel output contents.

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?

It gives clear operational context: use the same rebar/links that cs455_describe_section confirmed against the user's drawing, and notes it is read-only on the model. It does not explicitly state when to choose this over cs455_assess versus merely viewing assessment results, but the report-generation purpose is strongly implied.

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?