Skip to main content
Glama

Check a building scene for errors

cao_verifier
Read-only

WHEN a scene is composed and BEFORE cao_pdf / cao_generer_dxf / cao_rendu / cao_visite_plan / cao_visite_studio — the cheap check that stops a wrong plan or broken 4K visit from being delivered. FREE geometric audit of a CAO scene (no API key, 0 units). Detects the mistakes that make planches look wrong: openings.z used as absolute altitude instead of relative sill (allège), chien_assis dormers floating outside the roof, upper storey walls with no windows, guardrails far from the building, missing stairs between floors, openings overflowing their wall. ALSO checks that a staircase actually leads somewhere (escalier_traverse_mur — the flight runs into a partition of its own level; escalier_arrivee_hors_batiment — it lands outside the walls). STAIRCASE PLACEMENT is checked in full, because a stair dropped in an absurd spot is the most visible flaw of an AI-composed model: escalier_depart_hors_batiment (it starts in the void), escalier_volee_hors_batiment (the flight leaves the building on the way up), escalier_bloque_ouverture (it seals a doorway), escalier_z_hors_niveau (it floats between two slabs), escalier_hauteur_incoherente (it stops short of the floor above), escalier_chevauche (two flights in the same footprint), and escalier_sans_appui (free-standing mid-room — a WARNING, not blocking: an open stairwell is a legitimate choice). Each one comes with a correctifs[] entry carrying a REAL replacement position (x/y/rotation): the closest valid spot to what you asked for, backed against a wall, arriving in clear space and blocking no door. Apply with REST /api/v1/cao/integrite {appliquer:true, revalider:true} — you never have to guess where to put it. ALSO checks that a dormer sits on the slope (lucarne_profondeur_courte / _longue / lucarne_trop_haute — depth must be ≈ height / roof pitch, otherwise its roof floats above the slope or overshoots the ridge). Returns {ok, erreurs_schema, alertes[{code,severite,message,corriger}], conseils, resume}. Fix severite=critique before delivery. ALSO runs a full STRUCTURAL INTEGRITY check (is the building really closed and roofed?): enveloppe_percee — a wall end joins nothing (T-junctions and door jambs are recognised, so no false alarms) — murs_composantes_isolees — closed wall clusters / pillars / low walls scattered OUTSIDE the main envelope (the 'murs en vrac' Visite 4K defect; correctifs propose null = delete that wall) — bande_ouverte_entre_niveaux, mur_etage_sans_appui, toit_ouvert, toiture_sous_les_murs, ouvertures_chevauchantes, and the VOLUME CLASHES the IFC clash detector sees: mur_en_double, murs_superposes, mur_dans_une_baie (correctif slides the opening clear), volume_traverse_un_mur, volume_traverse_le_plafond, murs_qui_se_croisent (warning); pipe × wall crossings come back in reservations (sleeves to plan, not clashes). ALSO dalle_flottante / pilier_detache on orphan boxes. It returns integrite.correctifs[]: the exact field to write and the value to write there, e.g. {cible:'murs[3].x2', actuel:10400, propose:11000, raison:…} or {cible:'murs[12]', propose:null} to remove clutter. REST /api/v1/cao/integrite runs that check alone and can APPLY the fixes for you (appliquer:true, revalider:true) — also free, no key. Response includes regles_archi (buildingSMART-inspired principles). ALSO checks DOCUMENT COMPLETENESS (documents): the PDF planche delivers one full plan PER STOREY — 4 storeys means 4 complete plans — so it flags element_hors_plan (a stair/guardrail whose z attaches to no storey: it would vanish from EVERY plan), niveau_non_desservi (no stair ARRIVES at that storey and no lift covers it), arrivee_sans_protection (stair head without guardrail, NF P01-012), hauteur_niveau_insuffisante (<2200 mm). documents.couverture is the announced table of contents of the planche. Standalone: REST /api/v1/cao/documents (free, supports appliquer/revalider too). REST equivalent: /api/v1/cao/verifier.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
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. Changed5 schema fields changed
    • addedInput schema / properties / compositions
      Added value: +{
      +  "description": "Named 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.",
      +  "type": "object"
      +}
    • addedInput schema / properties / georef
      Added value: +{
      +  "description": "Optional 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.",
      +  "properties": {
      +    "altitude": {
      +      "description": "Orthogonal height in metres (NGF-IGN69 for Lambert-93).",
      +      "type": "number"
      +    },
      +    "crs": {
      +      "description": "Projected CRS name. Default EPSG:2154 (Lambert-93).",
      +      "type": "string"
      +    },
      +    "est": {
      +      "description": "Easting in metres in the CRS. Omit if unknown — never invent.",
      +      "type": "number"
      +    },
      +    "nord": {
      +      "description": "Northing in metres in the CRS. Omit if unknown — never invent.",
      +      "type": "number"
      +    },
      +    "orientation": {
      +      "description": "Angle in degrees of the project's X axis from map East, counterclockwise. Default 0.",
      +      "type": "number"
      +    }
      +  },
      +  "type": "object"
      +}
    • addedInput schema / properties / murs / items / properties / composition
      Added value: +{
      +  "description": "Optional key into the scene-level compositions object. When omitted, the exporter infers mur_exterieur / refend / cloison from geometry. A matching declared composition drops the Hypothese flag in the IFC.",
      +  "type": "string"
      +}
    • addedInput schema / properties / murs / items / properties / couches
      Added value: +{
      +  "description": "Optional inline material layers [{cle, epaisseur?}]. cle is one of enduit, bloc_beton, isolant, ba13, ossature, enduit_platre, beton_arme, tuile, charpente, etancheite. Omit epaisseur on the load-bearing layer so it takes the remainder of the wall thickness.",
      +  "type": "array"
      +}
    • addedInput schema / properties / murs / items / properties / materiau
      Added value: +{
      +  "description": "Optional single material key: the whole thickness becomes one load-bearing layer instead of a type composition.",
      +  "type": "string"
      +}
  4. Changed22 schema fields changed
    • changedInput schema / properties / boites / description
      Previous value: -"Boxes (furniture, volumes): center x,y + dims l,p,h (mm)"New value: +"Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[]."
    • addedInput schema / properties / boites / items / properties / h / description
      Added value: +"Height along Z (mm)"
    • addedInput schema / properties / boites / items / properties / l / description
      Added value: +"Length along X before rotation (mm)"
    • addedInput schema / properties / boites / items / properties / p / description
      Added value: +"Depth along Y before rotation (mm)"
    • addedInput schema / properties / boites / items / properties / rotation / description
      Added value: +"Rotation around the box centre, in DEGREES counter-clockwise (not radians). Default 0"
    • addedInput schema / properties / boites / items / properties / x / description
      Added value: +"Centre X of the box (mm) — not a corner"
    • addedInput schema / properties / boites / items / properties / y / description
      Added value: +"Centre Y of the box (mm) — not a corner"
    • addedInput schema / properties / boites / items / properties / z / description
      Added value: +"Underside height above the floor (mm). 0 = resting on the floor; raise it for a wall unit or a shelf"
    • changedInput schema / properties / murs / description
      Previous value: -"Walls: plan segments extruded vertically"New value: +"Walls: 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."
    • addedInput schema / properties / murs / items / properties / epaisseur / description
      Added value: +"Wall thickness (mm), spread evenly on both sides of the axis — the axis is the centreline, not a face. Default 200"
    • addedInput schema / properties / murs / items / properties / hauteur / description
      Added value: +"Wall height (mm) from floor level. Default 2500, a usual French ceiling height"
    • addedInput schema / properties / murs / items / properties / x1 / description
      Added value: +"Start point X of the wall axis (mm)"
    • addedInput schema / properties / murs / items / properties / x2 / description
      Added value: +"End point X of the wall axis (mm)"
    • addedInput schema / properties / murs / items / properties / y1 / description
      Added value: +"Start point Y of the wall axis (mm)"
    • addedInput schema / properties / murs / items / properties / y2 / description
      Added value: +"End point Y of the wall axis (mm)"
    • addedInput schema / properties / ouvertures / items / properties / hauteur / description
      Added value: +"Opening height (mm), measured up from `z`. `z + hauteur` must stay under the wall height"
    • addedInput schema / properties / ouvertures / items / properties / largeur / description
      Added value: +"Opening width (mm) measured along the wall, from `position`. Must fit inside the wall segment"
    • changedInput schema / properties / plan / description
      Previous value: -"2D reference lines"New value: +"2D reference lines — drawn flat, never extruded and never counted in the quantities. Use them for axes, plot limits or setting-out marks."
    • addedInput schema / properties / plan / items / properties / x1 / description
      Added value: +"Start X (mm), same frame as murs[]"
    • addedInput schema / properties / plan / items / properties / x2 / description
      Added value: +"End X (mm), same frame as murs[]"
    • addedInput schema / properties / plan / items / properties / y1 / description
      Added value: +"Start Y (mm), same frame as murs[]"
    • addedInput schema / properties / plan / items / properties / y2 / description
      Added value: +"End Y (mm), same frame as murs[]"
  5. Changed4 schema fields changed
    • addedInput schema / properties / cercles / description
      Added value: +"Circles 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."
    • addedInput schema / properties / cercles / items / properties / r / description
      Added value: +"Radius, same unit as plan[]"
    • addedInput schema / properties / cercles / items / properties / x / description
      Added value: +"Centre X, same unit as plan[]"
    • addedInput schema / properties / cercles / items / properties / y / description
      Added value: +"Centre Y, same unit as plan[]"
  6. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only declare the read-only/no-destroy profile, and the description goes far beyond that: it is FREE with no API key, returns {ok, erreurs_schema, alertes[...], conseils, resume}, distinguishes severite=critique blocking errors from WARNING-level ones (e.g. escalier_sans_appui), and describes the correctifs[] payloads with field-level targets. This is rich behavioral context beyond structured data, and it stays consistent with readOnlyHint=true.

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 WHEN/BEFORE clause is correctly front-loaded, but the body is an unusually long, run-on enumeration of every error code that could be tightened considerably. Much earns its place, yet the density and repeated framing ('ALSO checks…') hurt scannability.

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?

For a 12-parameter, deeply nested schema with no output schema, the description carries the return-shape burden well, spelling out the alert codes, severity semantics, correctifs structure, and the separate REST endpoints for the embedded checks. An agent has enough to call it and interpret results correctly.

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 input parameters are fully documented in the schema itself. The description adds meaning mostly about outputs/error codes rather than the 12 input params, so the baseline 3 is appropriate — it does not compensate for anything because there is nothing to compensate for.

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+resource (check/audit a CAO building scene) and immediately distinguishes itself by prescribing its position in the workflow. The agent can tell this is the pre-flight validator versus cao_pdf/cao_generer_dxf/cao_rendu/cao_visite_* generators without opening any schema.

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?

"WHEN a scene is composed and BEFORE cao_pdf / cao_generer_dxf / cao_rendu / cao_visite_plan / cao_visite_studio" gives explicit when-to-use and names the alternatives it gates. It further clarifies that fixing is a separate REST step (cao/integrite appliquer:true), leaving no ambiguity about sequencing.

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