Skip to main content
Glama

MIDAS CIVIL NX tools (MIDAS IT Europe)

Section Designer — check and draw a section

section_preview
Read-only

Checks a cross-section's outlines with Section Designer's own rules (closed, not self-crossing, holes inside their outline, no overlaps, materials) and returns a PNG drawing of it — the outlines, numbered input vertices, the centroid and chain dimensions — plus the extents, areas and every vertex. Use it FIRST, and LOOK at the drawing: compare it with the user's sketch (overall width and depth, slab and web thicknesses, haunches, cells) and correct misreads before computing or writing anything. Needs no model. From a sketch: read every dimension and put the outline down as vertices in y (across, right +) and z (up), in the sketch's units (default mm). Holes are separate rings inside their outline; direction of travel does not matter. Rounded corners: fillet on that vertex; arcs between vertices: bulge; round bars or ducts: { circle }. Standard shapes can use a template (i_girder, box_girder) instead of vertices. Two materials (girder + slab): one part each, in construction order, each with its material.

Input Schema

NameRequiredDescriptionDefault
svgNoAlso store the drawing as an SVG file and return its link.
sectionYesThe section, read off the sketch. Axes: y across (positive right), z up, as seen in CIVIL's section dialog; put the origin anywhere convenient (e.g. bottom-left corner or soffit centre) — CIVIL's frame is applied on write.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations declare readOnlyHint=true, and the description adds rich behavioral context beyond that: it checks outlines against specific rules, returns a PNG drawing plus extents, areas and every vertex, and requires no model. This gives an agent a complete picture of what the tool does and does not do.

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 long but front-loaded with purpose and usage instructions. Each sentence contributes useful guidance for a complex nested schema, though some phrasing could be tightened slightly without losing 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?

No output schema exists, and the description fully explains the return value (PNG drawing with outlines, vertices, centroid, chain dimensions, extents, areas, and every vertex). It also covers the 'no model needed' context and the construction-order requirement for materials, leaving nothing essential missing for correct invocation.

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 100%, so the schema documents all parameters. The description adds substantial meaning for the core 'section' parameter: coordinate axes (y across, z up), units (default mm), how to represent holes, fillets, bulges and circles, and how to structure parts and materials. It does not elaborate on secondary parameters like svg or warpingEffect, keeping it just below full marks.

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?

States a specific verb ('Checks') and resource ('cross-section's outlines') and explicitly lists the rules checked. It also distinguishes itself from siblings by saying 'Use it FIRST' and 'Needs no model', contrasting with section_properties and section_write without naming them.

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?

Explicitly says 'Use it FIRST' and describes the workflow: compare the drawing with the sketch and correct misreads before computing or writing anything. It does not name alternative tools, but the context precludes use of computation or write tools before this preview.

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