Skip to main content
Glama

MIDAS CIVIL NX tools (MIDAS IT Europe)

Beam to Plate — which beams and sections can convert

b2p_survey
Read-only

Reads the model the way the Beam to Plate plugin (1.0.6) does and studies every section the chosen beams use, against CIVIL NX's own published properties (/ope/SECTPROP): whether the outline was READ correctly (A/Iyy/Izz vs published) and how far the PLATE model sits from it, the verdict (converts / blocked / not read, with the reason), the plugin's plate-or-solid suggestion with the mesh a solid would need, material slots of composite parts, the model's length/force units, the beams that cannot be converted and why, and an element estimate for the mesh. Choose beams with ONE of elementIds, sections, groups or useCivilSelection (default: every beam). Read-only; on the website it runs as a background job (poll job_status).

Input Schema

NameRequiredDescriptionDefault
modelNoconvert = plates/solids along the member; slice = a transverse slice of each section meshed in its own plane (beams kept, nothing linked or loaded).convert
facetsNoFacets per circle for round sections.
groupsNoEvery beam in these structure groups.
meshAsNoPer-section override of the suggestion, {sectionId: 'plate'|'solid'}.
longSizeNoMesh size along the member (default 0.5 m), in the model's length unit (b2p_survey reports it).
sectionsNoEvery beam of these section ids.
calibrateNoAdjust plate thicknesses so the mesh has the section's own A, centroid, Iyy, Izz: where the shape is idealised (generic), every section, or never.generic
solidModeNoauto = each section as the plugin suggests (solid for compact concrete, plates for thin walls); plate; solid.auto
transSizeNoMesh size across the section (default 0.25 m), in the model's length unit (b2p_survey reports it).
elementIdsNoBeam element ids: "101-118, 205" or [101, 102].
solidPlatesNoHow a solid (concrete) section meshed as PLATES is idealised: grid of plates over the real section; thin plates round the outline; one plate per wall.grid
sectionLimitNoHow many section cards to return.
acceptSectionsNoSection ids to convert although their check failed (the window's 'Convert anyway'). Only with the user's agreement.
useCivilSelectionNoThe elements selected in CIVIL NX right now.
includeUncountedStiffenersNoAlso mesh stiffeners CIVIL NX leaves out of the section (the 'C' box unticked).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare read-only and closed-world; the description adds real behavioral context beyond that — the plugin-version fidelity criterion, the comparison source (/ope/SECTPROP), the enumerated verdicts with reasons, and the background-job/polling mode on the website. Pagination and response shape are not described, and no output schema exists, which keeps it off a 5.

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

Conciseness3/5

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

The purpose is front-loaded, but the opening sentence is an extremely long comma-chained enumeration of every output field, and the selector constraint only appears after it. The content earns its place, but the structure makes it harder to scan than it needs to be.

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?

With 15 parameters, nested objects and no output schema, the description does the work of explaining what the tool returns (verdicts, reasons, suggestions, material slots, units, element estimate). Selector exclusivity and the background-job behavior are covered. Only pagination/response envelope details are left unspecified.

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 100%, so baseline is 3, and the description earns a point above it by stating a constraint the schema does not: the four beam selectors are mutually exclusive, use ONE of them, with 'every beam' as the default. That is genuine meaning added over the structured fields.

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 and resource: it reads the model as the Beam to Plate plugin (1.0.6) does and surveys each section against CIVIL NX's published /ope/SECTPROP properties to produce a convert/blocked verdict. This is clearly a diagnostic pass, distinguishable from the mutating sibling b2p_convert, and no schema needs opening to know what it produces.

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 tells the agent how to scope the run ('Choose beams with ONE of elementIds, sections, groups or useCivilSelection (default: every beam)') and warns that acceptSections must only be used with the user's agreement. It also notes the website deployment runs as a background job to be polled with job_status. It stops short of explicitly saying 'run this before b2p_convert', which is the natural next step an agent would need.

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