Skip to main content
Glama

Prepare building-permit figures and documents

cao_permis
Read-only

WHEN a detached house is headed for a French BUILDING PERMIT (permis de construire, Cerfa 13406). Drafts the permit file from the CAO scene: the Cerfa figures (surface de plancher per R111-22 — inner face of façades, stair openings and parts under 1.80 m excluded; emprise au sol per R420-1; eaves and ridge heights; storeys), plus PCMI2 site plan, PCMI3 section, PCMI4 written notice and PCMI5 elevations. PCMI1, PCMI6, PCMI7 and PCMI8 (location map, landscape insertion, photos) are listed as 'à fournir' — never invented; a Géoportail link is given when the scene has georef. For an EXTENSION, mark the existing walls existant: true: existing and created areas are then separated, and the file says when a déclaration préalable is enough (up to 20 m² created, 40 m² in a PLU urban zone). Local zoning rules (PLU) are NOT checked. Call cao_verifier first. Returns JSON {cerfa, pieces[], notice[], alertes[], avertissement}; drawings are SVG strings.

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.
coupeNoOptional section line AA as [x1, y1, x2, y2] in mm (CAO axes). Default: across the building through its stair.
titreNoProject title shown on the dossier's cover page.
auteurNoOptional: applicant or designer shown on the cover page.
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. Added

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive, and the description adds substantial behavior beyond them: which PCMI pieces are never invented, the Géoportail link condition on `georef`, the déclaration préalable thresholds, and the exact return shape (cerfa, pieces[], notice[], alertes[], avertissement with SVG drawings).

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?

Dense but well front-loaded, opening with the WHEN trigger before the mechanics. Nearly every clause carries information (regulatory references, piece names, fallbacks), though the sentence count is on the heavy side for a description that also has rich schema support.

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?

With no output schema, the description steps in by naming the returned JSON keys and noting drawings are SVG strings. Combined with the computation rules and regulatory bases, an agent has everything needed to invoke and interpret the tool 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 coverage is 100%, so the schema already documents all 15 parameters thoroughly. The description reinforces the `existant` flag semantics for extensions and mentions `georef`, but adds little beyond what the schema already states. Baseline 3 is appropriate.

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 — drafting the French permis de construire file (Cerfa 13406) from the CAO scene — and enumerates exactly which figures and PCMI pieces are produced. This clearly separates it from siblings like cao_pdf, cao_metres, or cao_urbanisme.

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?

Explicit trigger ('WHEN a detached house is headed for a BUILDING PERMIT'), an extension branch with the `existant: true` instruction, a prerequisite ('Call cao_verifier first'), and an explicit exclusion ('Local zoning rules (PLU) are NOT checked'). Routing conditions are fully specified.

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