Skip to main content
Glama

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

Check an IFC model against IDS requirements

cao_ids_verifier
Read-only

WHEN a BIM manager's information requirements (an IDS 1.0 file, buildingSMART) must be checked on a model before delivery — ours built from the scene, or an architect's IFC: checks every specification (entity, attribute, property compared in SI units, classification, material, partOf; required, optional, prohibited; target IFC version) and returns, per specification, the applicable elements and those failing with their reasons; bcf: true adds the failures as BCF 2.1 topics with their objects. Without ids, checks our French housing IDS (rooms with net, habitable and Carrez areas, typed doors and windows, accessibility, load-bearing walls with materials, storeys, stairs, Lambert-93), free at GET /api/v1/cao/ifc/ids/logement-fr.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bcfNoTrue to add the failures as a BCF 2.1 zip in base64 (bcf_base64).
idsNoOptional IDS 1.0 XML text; default: our French housing IDS.
ifcNoOptional IFC text (STEP) to check instead of the scene; an architect's model keeps its GlobalIds.
mursNoWalls: plan segments extruded vertically. Every coordinate in this whole scene is in MILLIMETRES, in a single plan frame whose origin you choose — X to the right, Y upward, Z up from the floor. Keep one consistent origin across murs/boites/plan: the generators never recentre anything for you.
planNo2D reference lines — drawn flat, never extruded and never counted in the quantities. Use them for axes, plot limits or setting-out marks.
boitesNoBoxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[].
georefNoOptional Lambert-93 (EPSG:2154) false origin for IfcMapConversion. Local millimetres are scaled by 0.001 to CRS metres. Do not invent coordinates: omit est/nord if unknown (origin stays 0). orientation is the angle in degrees of project X from map East, counterclockwise.
cerclesNoCircles on the 2D plan, alongside plan[] lines: each has a centre and a radius, in the same unit as the plan. Use for round shapes a polyline would render badly — fillets, posts, manholes.
reseauxNoPlumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type).
toituresNoRoofs — used only by cao_pdf. WITHOUT this field: a flat roof is auto-generated over the footprint of ALL walls (legacy default). WITH it: compose freely — each entry can target a subset of walls (via `murs`), letting you build an L-shaped building's roof, or add a dormer on top of a main roof.
plomberieNoSanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite.
decorationNoPaint/finish per wall — used only by cao_pdf. Colors the elevations (exterior face) and the axonometric view (face auto-detected by orientation relative to the building's centroid).
ouverturesNoDoors/windows embedded in a wall — used only by cao_pdf (elevations + axonometric view), no effect on dxf/metres.
electriciteNoElectrical symbols (outlets, switches, lights…) — used only by cao_pdf (dedicated technical plan + quantities), no effect on dxf/metres/render. Position: attached to a wall (`mur`+`position`, like ouvertures) or free (`x`,`y`).
compositionsNoNamed wall/slab layer sets declared by the project. A key that matches an inferred kind (mur_exterieur, refend, cloison, plancher, toiture) or murs[].composition drops the Hypothese flag. Each value is {libelle, couches: [{cle, epaisseur?}]}. cle: enduit, bloc_beton, isolant, ba13, ossature, enduit_platre, beton_arme, tuile, charpente, etancheite. Omit epaisseur on the load-bearing layer.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / murs / items / properties / existant
      Added value: +{
+  "description": "Optional: true for a wall of the EXISTING building when the scene is an extension. cao_permis then counts as created only what the works add.",
+  "type": "boolean"
+}
  2. Changed1 schema field changed
    • changedInput schema / properties / plomberie / items / properties / type / enum
      Previous value: -[
-  "baignoire",
-  "chauffe_eau",
-  "compteur_eau",
-  "douche",
-  "evier",
-  "lavabo",
-  "radiateur",
-  "wc"
-]New value: +[
+  "baignoire",
+  "chauffe_eau",
+  "compteur_eau",
+  "douche",
+  "evier",
+  "lavabo",
+  "module_hydraulique",
+  "pac_exterieure",
+  "radiateur",
+  "wc"
+]
  3. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered; the description adds real behavior beyond that — per-specification output with failing elements and reasons, and that `bcf: true` produces BCF 2.1 topics. It could have clarified it never mutates the input and what the base64 payload entails, so 4 rather than 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?

Front-loads the WHEN clause, which is good, but the body collapses specification scope, return shape and the default-IDS note into one dense, dash-heavy run-on sentence that is hard to parse. Nearly every clause carries content, but the packaging works against readability.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description must carry return semantics; it does describe per-specification results and BCF output. However, with 15 parameters dominated by scene-construction fields (murs, boites, toitures, ouvertures…), the description never explains how those inputs feed the check, leaving a substantial mismatch between the described tool and its actual schema unaddressed.

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 description coverage is 100%, so the schema already documents every parameter; baseline is 3. The description clarifies the semantics of `ids` (default French housing IDS) and `bcf` (adds failures as BCF topics), but does not touch the many scene-construction parameters (murs, boites, plan, etc.), which is the bulk of the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: check an IFC model against an IDS 1.0 requirements file, with a precise enumeration of what is checked (entity, attribute, property, classification, material, partOf). It differentiates itself from the many cao_* siblings by naming IDS conformance specifically. It does not explicitly contrast with the closest siblings (cao_valider_ifc, cao_verifier, cao_conflits_ifc), so a 4 rather than 5.

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?

Gives a clear triggering condition ('WHEN a BIM manager's information requirements must be checked on a model before delivery') and clarifies the fallback path (no `ids` = French housing IDS). It distinguishes the two input modes (scene-built model vs. architect's IFC). No explicit when-not or named alternatives, so 4.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All immobilier toolsInspect
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