Skip to main content
Glama

Plan a 4K walkthrough camera path

cao_visite_plan
Read-only

WHEN the building should be SEEN in motion rather than read on a flat plan — you direct the shot. IMPORTANT: call cao_verifier FIRST and fix every severite=critique (intégrité clos/couvert + escalier/lucarne). This endpoint REFUSES with HTTP 400 construction_critique if the scene still has critical construction defects — the 4K visit would show them. Apply fixes via REST /api/v1/cao/integrite {appliquer:true, revalider:true} then retry. DIRECT the 4K cinematic visit of a CAO scene: choose the LENS (focal length in mm, full-frame equivalent) and the CAMERA PATH. Returns a shooting plan {plan:{objectif, cadence, plans[], chemin[]}, alertes[], resume} where chemin is the full waypoint list (position/vise in mm, CAO axes x=right y=depth z=height). Rooms are detected automatically (walls → flood fill → room centres → path through doorways), one interior walk per storey plus the stair climb. Rendering is done by ONE engine, the browser GPU: paste plan into CAO editor → « Visite 4K » → « Plan de caméra piloté », or call window.CAD_startCinematicTour({plan}). To adjust: resend with a modified objectif/cadence, or send back an edited chemin (it is then used verbatim and checked). Lens catalogue (free, no key): GET /api/v1/cao/visite/objectifs. Requires API key. REST: /api/v1/cao/visite/plan.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
fpsNoImages par seconde de la visite. 24 à 30 pour un rendu naturel ; au-delà, le fichier grossit sans gain visible.
modeNo'deco' = furnished as modelled; 'nu' = bare shell (plaster).deco
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[].
cheminNoOPTIONAL: your own waypoints — replaces the computed path.
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.
cadenceNoPacing. Interior is a WALK: above ~1600 mm/s the video is unwatchable.
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.
duree_sNoVideo length, 8–900 s (default 60). A real estate walkthrough runs 480–600 s; the path is ENRICHED with extra exterior revolutions to fill it with movement rather than slowed down.
reseauxNoPlumbing pipe runs (EF/EC/EU/EV/EP/chauffage) — used only by cao_pdf (technical plan + linear-meter quantities per type).
objectifNoLens, full-frame equivalent mm. 20 = interior standard, 35 = exterior, 50 = closing shot. Below 16 mm the image goes fisheye.
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.
resolutionNoDéfinition du rendu — « 1080p » ou « 4k ». La 4K quadruple le temps de calcul.4k
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. Changed6 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[]"
    • addedInput schema / properties / fps / description
      Added value: +"Images par seconde de la visite. 24 à 30 pour un rendu naturel ; au-delà, le fichier grossit sans gain visible."
    • addedInput schema / properties / resolution / description
      Added value: +"Définition du rendu — « 1080p » ou « 4k ». La 4K quadruple le temps de calcul."
  6. Changed1 schema field changed
    • changedInput schema / properties / duree_s / description
      Previous value: -"Video length, 8–300 s (default 60)"New value: +"Video length, 8–900 s (default 60). A real estate walkthrough runs 480–600 s; the path is ENRICHED with extra exterior revolutions to fill it with movement rather than slowed down."
  7. Changed1 schema field changed
    • changedInput schema / properties / cadence / properties / hauteur_oeil_mm / default
      Previous value: -1620New value: +1650
  8. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true/destructiveHint=false, and the description adds real behavioral context beyond them: it REFUSES with HTTP 400 construction_critique on unresolved defects, requires an API key, and explains that a supplied chemin is used verbatim and checked. It does not cover rate limits or runtime cost beyond noting 4K rendering happens in the browser.

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?

Front-loads the WHEN and the cao_verifier prerequisite, then the refusal contract, then the deliverable and how to iterate. Dense and long, but for a 19-parameter planning endpoint nearly every sentence carries actionable content; a few lines (lens catalogue URL, REST path) are utility rather than guidance.

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 still describes the return shape ({plan:{objectif,cadence,plans[],chemin[]}, alertes[], resume}), the automatic room-detection pipeline, the rendering engine and both invocation routes, plus prerequisites and error behavior — everything an agent needs to call and consume this tool.

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, but the description adds operational meaning: lens values are full-frame mm (20 interior standard, 35 exterior, 50 closing; below 16 goes fisheye), chemin is the waypoint list with position/vise in mm and CAO axes x=right y=depth z=height, and an edited chemin overrides the computed path.

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+resource: it produces a 4K cinematic camera-path plan for a CAO scene, and details what you choose (lens, camera path) and what comes back (plan.chemin waypoints). It names cao_verifier as a gating sibling, though it never explicitly contrasts itself with cao_visite_camera, so differentiation is implied rather than stated.

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?

Gives an explicit WHEN ('when the building should be SEEN in motion rather than read on a flat plan'), an ordering prerequisite (call cao_verifier FIRST and fix severite=critique), the exact remedy path (REST /api/v1/cao/integrite {appliquer:true,revalider:true} then retry), and how to iterate (resend with modified objectif/cadence, or return an edited chemin).

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