immobilier

Generate an IFC (BIM) model

cao_generer_ifc

Read-only

WHEN the drawing must leave as a real BIM file, openable in Revit/ArchiCAD/Solibri — not just a drawing. Draw a building scene and get an IFC4 file in millimetres: real spatial hierarchy (project/site/building/storeys), STABLE IFC GlobalIds (the same model keeps them across exports; pass projet_id; imported elements keep theirs), structural columns and beams (poteaux[], poutres[] become IfcColumn, IfcBeam; see GET /cao/schema), one named IfcSpace per room with its areas (floor, French habitable and Carrez), floor slabs cut by their stair openings, an IfcRoof, IfcStair flights, standard Pset/Qto quantities, and material layers carrying density and thermal conductivity. Wall/slab/door/window types, 2nd-level space boundaries, and Lambert-93 georeferencing (EPSG:2154, Scale 0.001) are included so Revit/Archicad can open a typed, located model. Declare compositions{} to replace type compositions. Doors/windows really cut their host wall (IfcOpeningElement + IfcRelFillsElement). Passes IFC4 schema and EXPRESS-rule validation. Validate locally with cao_valider_ifc (no buildingSMART account). Call cao_verifier first. Same scene as cao_generer_dxf. Returns a JSON object {ifc, elements, unites, schema}: the IFC file arrives INLINE as text in ifc — no download URL, nothing stored server-side, so write it to a .ifc file yourself. elements counts the IFC objects emitted and schema names the IFC version produced. Set armatures: true to add the reinforcement: IfcReinforcingBar with exact geometry for footings and lintels (aggregated to their host), one IfcReinforcingMesh per slab.

Input Schema

TableJSON Schema

Name	Required	Description
`murs`	No	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.
`plan`	No	2D reference lines — drawn flat, never extruded and never counted in the quantities. Use them for axes, plot limits or setting-out marks.
`boites`	No	Boxes (furniture, volumes): a rectangular block placed by its CENTRE, not by a corner. Millimetres, same frame as murs[].
`georef`	No	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.
`cercles`	No	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.
`reseaux`	No	Plumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type).
`toitures`	No	Roofs — 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.
`armatures`	No	Add the reinforcement computed per Eurocode 2 (bars and slab meshes).
`plomberie`	No	Sanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite.
`decoration`	No	Paint/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).
`ouvertures`	No	Doors/windows embedded in a wall — used only by cao_pdf (elevations + axonometric view), no effect on dxf/metres.
`electricite`	No	Electrical 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`).
`compositions`	No	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.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / armatures

Added value: +{
+  "default": false,
+  "description": "Add the reinforcement computed per Eurocode 2 (bars and slab meshes).",
+  "type": "boolean"
+}

Changed1 schema field changedSep 15, 2026

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"
+}

Changed1 schema field changedSep 14, 2026

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"
+]

Changed5 schema fields changedSep 13, 2026

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"
+}

Changed22 schema fields changedSep 12, 2026

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[]"
```

Changed4 schema fields changedSep 7, 2026

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[]"
```

AddedAug 11, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the readOnly/destructive annotations: it discloses that the IFC returns inline with no download URL and nothing stored server-side, that GlobalIds are stable across exports when projet_id is passed, that doors/windows really cut host walls, that output passes schema/EXPRESS validation, and that armatures adds Eurocode-2 reinforcement. This is exactly the behavioral context annotations cannot carry.

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 'WHEN…' clause is front-loaded and the content is dense but largely earns its place for a 13-parameter, nested, no-output-schema tool. However several ideas are crammed into single run-on sentences (the return-value and armatures points could be separated), which reduces 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?

Given no output schema and a complex nested input, the description compensates fully: it explains the returned object shape ({ifc, elements, unites, schema}), how the inline IFC must be written to disk, the units, georeferencing, and the validation guarantees. An agent has everything needed to invoke and consume the result.

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 baseline is 3; the description still adds meaning by naming parameters and their effect beyond the schema text (projet_id for GlobalId stability, compositions{} to replace type compositions, armatures:true for IfcReinforcingBar/IfcReinforcingMesh, poteaux[]/poutres[] becoming IfcColumn/IfcBeam). It also references parameters (poteaux, poutres, projet_id) not present in the shown schema, which is slightly confusing.

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?

Names a specific verb and resource ('Draw a building scene and get an IFC4 file in millimetres') and enumerates the concrete IFC output (spatial hierarchy, IfcColumn/IfcBeam, IfcSpace, IfcRoof, IfcStair, Pset/Qto). It also distinguishes itself from siblings, explicitly contrasting with cao_generer_dxf ('Same scene as cao_generer_dxf') and pointing to cao_valider_ifc/cao_verifier.

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?

States the triggering condition clearly ('WHEN the drawing must leave as a real BIM file, openable in Revit/ArchiCAD/Solibri — not just a drawing') and names the alternative path (cao_generer_dxf for the same scene, cao_valider_ifc to validate locally, cao_verifier to call first). When-to-use and sibling routing are both explicit.

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

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