Skip to main content
Glama

Adjust one walkthrough camera view

cao_visite_camera
Read-only

WHEN the automatic visit is good but ONE view is wrong — the façade is cut off, the ridge is out of frame, you want to step into the next room — and rewriting a whole chemin by hand would be absurd. PILOT the camera with a SEQUENCE OF ACTIONS instead of coordinates: ['avancer x3', 'pivoter_gauche', 'monter', 'zoom_arriere']. Actions are named (avancer, reculer, gauche, droite, the four diagonals, monter, descendre, pivoter_gauche/droite, incliner_haut/bas, zoom_avant, zoom_arriere, vue_initiale, vue_ensemble, piece_suivante, piece_precedente) or given as the KEYBOARD SHORTCUT a human would press in the render studio ('ctrl+8' = forward, numeric keypad laid out as a compass rose). Same grammar both ways, so a view prepared here is reproduced exactly by hand. Start from depuis (any waypoint of a chemin from cao_visite_plan) or omit it for an overall view. POST THE SCENE TOO: it enables wall collision (a step that would end inside a partition is refused and explained, not silently applied) and the room landmarks. Returns {camera, etapes[] (state after EACH action, with the reason for refused steps), chemin[]} — feed chemin straight back to cao_visite_studio to render that exact viewpoint in 4K. Catalogue of actions and keys (free, no key): GET /api/v1/cao/visite/commandes. Requires API key. REST: /api/v1/cao/visite/camera.

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[].
depuisNoStarting viewpoint — same shape as a `chemin` waypoint. Omit for an overall view of the building.
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.
actionsYesOrdered sequence. Each item is an action code ('avancer'), a keyboard shortcut ('ctrl+8'), a repeat form ('avancer x3'), or {code, repetitions}. 200 items max.
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).
reglagesNoStep sizes. Defaults: 500 mm per move, 250 mm per altitude step, 15° per rotation, ×1.25 per zoom. `grand_pas: true` = the Shift key (×4).
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
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered, yet the description still adds real behavioral context: posting the scene enables wall collision, refused steps are 'refused and explained, not silently applied', an API key is required, the 200-item action cap, and the exact return shape. Not a 5 only because it never says what happens to an existing stored view or where `depuis` state lives.

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?

It is long and laden with ALL-CAPS emphasis, but the trigger condition is front-loaded and every clause carries operational information (action grammar, scene posting, return contract). Nothing is pure filler; it is dense rather than bloated.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 15-parameter tool with nested objects, no output schema, and a shared scene-geometry schema, the description supplies the crucial missing link — that the murs/boites/etc. parameters are there to enable collision and landmarks — plus the return contract. It is nearly complete; only the role of `reglages` and of the non-scene rooms fields is left implicit.

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 meaningfully enriches the schema: it enumerates the action vocabulary, the keyboard-shortcut aliasing ('ctrl+8' = forward, numpad as compass rose), the repeat form ('avancer x3'), the origin of `depuis`, and the purpose of posting scene fields. It does not explain `reglages`, which is the one schema block it leaves untouched.

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 states a specific verb and resource: adjust ONE camera view of a walkthrough by piloting the camera with a sequence of named actions rather than coordinates. It explicitly scopes itself against cao_visite_plan (which produces the `chemin`) and cao_visite_studio (which renders it), so an agent can distinguish it from siblings without opening schemas.

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?

The opening WHEN clause names the exact triggering situation ('the automatic visit is good but ONE view is wrong... rewriting a whole chemin by hand would be absurd') and names the two sibling tools to reach for instead at the relevant stages. When-to-use and alternatives are both explicit rather than inferred.

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