Skip to main content
Glama
Sign In

immobilier

by fr.synergieloc
OverviewDiscussionsAdmin

Get a verified example building scene

cao_demo
Read-only

WHEN you are about to draw ANY French building for the first time, or when a user asks for a plan / DXF / IFC and you have not yet used these tools — call this FIRST. It hands back a COMPLETE, ALREADY-VERIFIED scene (zero audit alerts) plus the exact next calls in order. FREE, no API key, 0 units. WHY IT MATTERS: composing a scene from the schema alone takes several round-trips and usually fails on the same mistakes (openings.z used as an absolute altitude instead of a relative sill, a storey with no windows). Starting from a working scene and editing it is faster and cannot fail. GOOD CALL: cao_demo {} -> the house; cao_demo {"exemple": "appartement"} for a flat with no roof; cao_demo {"exemple": "extension"} for a veranda grafted onto an existing facade. Then feed scene straight into cao_verifier, then cao_pdf / cao_generer_dxf / cao_generer_ifc. DO NOT: do not invent a scene from scratch before trying this; do not call it to CHECK a scene you already have (that is cao_verifier); do not expect a drawing back — this returns JSON, the drawing comes from the next call. All dimensions are MILLIMETRES.

Input Schema

NameRequiredDescriptionDefault
exempleNomaison = single-storey house with a two-slope roof; appartement = T3 flat, no roof; extension = veranda grafted onto an existing wallmaison

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / exemple / enum
      Previous value: -[
-  "maison",
-  "appartement",
-  "extension"
-]New value: +[
+  "maison",
+  "appartement",
+  "extension",
+  "projet_complet"
+]
  2. Added

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint true, destructiveHint false, openWorldHint false), and the description does not contradict them. It adds genuinely non-obvious context beyond annotations: it is free with no API key and 0 units, results are guaranteed zero-audit-alert, and it returns JSON rather than a drawing. It stops short of describing the shape/size of the returned scene object, which matters since there is no output schema.

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-loaded with the trigger condition ('call this FIRST'), then organised into WHY / GOOD CALL / DO NOT blocks that each carry distinct information. The all-caps emphasis and a few restated warnings ('do not invent a scene from scratch') cost some tightness but do not obscure the content.

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 correctly explains what comes back (a JSON scene, not a drawing), what units it uses (millimetres for all dimensions), and the exact downstream chain (scene -> cao_verifier -> cao_pdf / cao_generer_dxf / cao_generer_ifc). Nothing an agent needs to invoke it correctly is 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 coverage is 100% and the enum already documents maison/appartement/extension, so the description largely restates that. It adds practical invocation syntax and the implicit default (calling with no arguments yields the house), but the fourth enum value, projet_complet, is left unexplained in both the schema and the description.

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 concrete verb and resource: it returns a complete, already-verified example building scene as JSON, and shows the exact call syntax. It immediately separates itself from the sibling cao_verifier by scope (authoring starter vs. checking existing work), so an agent can pick it without opening either schema.

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 WHEN clause ('about to draw ANY French building for the first time', or a plan/DXF/IFC request before these tools have been used), explicit GOOD CALL examples for each variant, and a DO NOT section that names the correct alternative (cao_verifier) for checking existing scenes. Both inclusion and exclusion conditions are stated.

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