Skip to main content
Glama

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

cao_regles_structure_reseaux

WHEN a building scene must be completed with structure and building services by French rules before BIM export or quoting: lintels over openings of load-bearing walls, strip footings sized from service loads, slab span check (indicative pre-design, to be validated by a structural engineer); NF C 15-100 electrical points per room (outlets, RJ45, lighting with its switch, one smoke detector per level, panel with 30 mA RCD) and circuit count; single-flow mechanical ventilation per the 24 March 1982 decree (extract grilles in wet rooms, air inlets in dry rooms, fan, flows); drainage branches with slopes per NF DTU 60.11; water inlet and 200 L water heater placed where missing; room heat losses per NF EN 12831 and radiators sized at 55/45 °C (NF EN 442). Adds what is missing, never removes. Returns {scene, rapport, controles}; send scene to cao_generer_ifc to get IfcBeam, IfcFooting, IfcOutlet, IfcAirTerminal, IfcPipeSegment, IfcSpaceHeater…

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
solNoSoil assumptions for footings: {contrainte_mpa (default 0.20), hors_gel_mm (default 800)}.
vmcNoGenerate single-flow ventilation (extract grilles, air inlets, fan, flows).
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.
chauffageNoCompute room heat losses (NF EN 12831) and size radiators at 55/45 °C.
plomberieNoSanitary fixtures (sink, WC, shower…) — used only by cao_pdf. Same positioning as electricite.
structureNoGenerate lintels and strip footings, check slab spans.
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`).
evacuationsNoGenerate drainage branches to the stack with slopes (NF DTU 60.11).
alimentationNoPlace the water inlet and water heater when missing (NF DTU 60.11).
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.
electricite_reglesNoComplete electrical points per NF C 15-100.

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. Changed1 schema field changed
    • addedInput schema / properties / chauffage
      Added value: +{
+  "default": true,
+  "description": "Compute room heat losses (NF EN 12831) and size radiators at 55/45 °C.",
+  "type": "boolean"
+}
  4. Changed1 schema field changed
    • addedInput schema / properties / alimentation
      Added value: +{
+  "default": true,
+  "description": "Place the water inlet and water heater when missing (NF DTU 60.11).",
+  "type": "boolean"
+}
  5. Added

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden. It explicitly states 'Adds what is missing, never removes,' which is a key behavioral guarantee. It also lists specific elements added and notes that slab span checks are 'indicative pre-design, to be validated by a structural engineer.' It mentions the return structure. It does not detail potential side effects like overwriting existing data (though 'never removes' mitigates), but overall it is transparent about behavior.

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 well-structured: it front-loads the core purpose, lists the added elements in a readable sequence, and ends with the return value and next step. Every sentence adds value, though the length could be trimmed for quick parsing. It is more comprehensive than verbose, earning a 4.

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?

Given the tool's complexity (many regulatory additions) and no output schema, the description covers the main functionality and workflow well. However, it does not describe the contents of 'rapport' and 'controles' returned in the output, which is a gap. It also doesn't mention default behaviors for all parameters beyond the schema, but those are covered by the schema. For a tool of this scope, a 3 is appropriate because the output details are missing.

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 baseline is 3. The description provides high-level context (e.g., coordinates in millimetres, boxes placed by centre) but these details are already present in the schema's property descriptions. The tool description adds little per-parameter meaning beyond what the schema provides, so it does not exceed the baseline.

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?

The description clearly states the tool's purpose: 'WHEN a building scene must be completed with structure and building services by French rules before BIM export or quoting.' It specifies a concrete verb ('complete') and a resource ('building scene'), and enumerates the specific additions (lintels, footings, electrical points, ventilation, etc.). It also distinguishes itself from siblings by explicitly targeting pre-BIM/quoting preparation and pointing to cao_generer_ifc as the follow-up, making its role distinct from cao_pdf and other cao_* tools.

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?

The description opens with a clear 'WHEN' condition ('before BIM export or quoting') and instructs the agent to send the returned scene to cao_generer_ifc, establishing a workflow. However, it does not explicitly mention when not to use this tool (e.g., when only technical PDFs are needed without full IFC generation), leaving some ambiguity versus siblings like cao_pdf. Still, the primary use case is well-defined.

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