3D New Era AI

by leandrodaf

Overview Schema Source Related Servers Discussions Admin

Rust

Hybrid

Draw walls, rooms and more

create

Build walls, rooms, dimensions, labels, roofs, and solids in one atomic step for 3D architectural floor plans.

Instructions

Create walls (polylines; hs = height per point for gables), rooms (pts, or at=[x,y] to detect from walls; ceiling_flat=false follows wall profiles instead of the default flat ceiling), dims (a+b or wall id), labels, roofs (rectangle pts, gable|shed, pitch or ridge_h, eave h, overhang, gables=true closes the ends, skylights [{at,w,d}] cut glazed openings) and solids (pts outline raised by h at elev: slabs/mezzanines of any shape; or profile [[u,z]] swept from a to b: gables, ramps) in one atomic step.

Input Schema

TableJSON Schema

Name	Required	Description
`v`	No	Plan version (tab) to write to; switches to it first
`px`	No	Points are background-image pixels; lengths stay in cm
`dims`	No	Dimension lines: between two points, along a wall, or across a room
`exact`	No	Keep wall ends as given; no snap onto nearby walls
`roofs`	No	Pitched roofs over a rectangle, as one group of panels
`rooms`	No	Rooms: an outline of points, or `at` inside closed walls
`walls`	No	Walls, each a chain of points joined corner to corner
`labels`	No	Text on the plan
`solids`	No	Solids: outlines raised by `h` (slabs) or sections swept `a`→`b` (gables, ramps)
`polylines`	No	Free lines: annotations, arrows, electrical or plumbing runs

Output Schema

TableJSON Schema

Name	Required	Description	Default
`v`	No
`ok`	Yes
`ids`	No
`rev`	No
`text`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv3.1.0Oct 1, 2026

changedInput schema / $defs / RoofSpec / properties / ridge_h / description

Previous value: -"Height of the ridge (gable) or high side (shed) above the storey floor, cm"New value: +"Ridge (gable) or high side (shed) height above the floor, cm"

changedInput schema / $defs / RoomSpec / properties / ceiling_flat / description

Previous value: -"Ceiling flat at storey height (true, default) or following the wall profiles (false)"New value: +"Flat ceiling at storey height (default) or following wall profiles (false)"

changedInput schema / $defs / RoomSpec / properties / pts / description

Previous value: -"Floor polygon. Omit and give `at` to detect the room enclosed by walls"New value: +"Floor polygon; or omit and give `at`"

addedInput schema / properties / exact

Added value: +{
+  "description": "Keep wall ends as given; no snap onto nearby walls",
+  "type": "boolean"
+}

changedInput schema / properties / roofs / description

Previous value: -"Pitched roofs over a rectangle, built as one group of sloping panels"New value: +"Pitched roofs over a rectangle, as one group of panels"

changedInput schema / properties / solids / description

Previous value: -"Solids: plan outlines raised by `h` (slabs, decks) or cross-sections swept from `a` to `b` (gables, ramps)"New value: +"Solids: outlines raised by `h` (slabs) or sections swept `a`→`b` (gables, ramps)"

Changed22 schema fields changedv3.0.0Sep 30, 2026

removedInput schema / $defs / DimSpec / properties / chain / default
```
Removed value: -false
```
removedInput schema / $defs / DimSpec / properties / in3d / default
```
Removed value: -false
```

changedInput schema / $defs / Point2 / description

Previous value: -"[x, y] in centimeters; x grows right, y grows down"New value: +"[x, y] cm"

removedInput schema / $defs / PolylineSpec / properties / closed / default
```
Removed value: -false
```
removedInput schema / $defs / PolylineSpec / properties / curved / default
```
Removed value: -false
```
removedInput schema / $defs / PolylineSpec / properties / divider / default
```
Removed value: -false
```
removedInput schema / $defs / RoofSpec / properties / gables / default
```
Removed value: -false
```

changedInput schema / $defs / RoofSpec / properties / kind / description

Previous value: -"`gable` (two slopes, default; steep = A-frame) or `shed` (one slope rising from the pts[0]→pts[1] side)"New value: +"Default `gable` (steep = A-frame); `shed` rises from the pts[0]→pts[1] side"

addedInput schema / $defs / RoofSpec / properties / kind / enum
```
Added value: +[
+  "gable",
+  "shed"
+]
```

changedInput schema / $defs / RoofSpec / properties / skylights / description

Previous value: -"Glazed openings cut through the roof: center `at:[x,y]` on the plan, `w` along the ridge and `d` across it (plan size), cm"New value: +"Glazed roof openings: center `at`, `w` along the ridge, `d` across, cm"

changedInput schema / $defs / RoomSpec / properties / ceiling_flat / description

Previous value: -"Ceiling mode: true (default) is flat at storey height; false follows wall profiles. Lower roof panels clip either mode"New value: +"Ceiling flat at storey height (true, default) or following the wall profiles (false)"

changedInput schema / $defs / RoomUse / description

Previous value: -"Declared room program, independent of its display name. Auto preserves legacy name/equipment inference; other values are explicit intent"New value: +"Declared room program; `auto` infers it from the name and equipment"

changedInput schema / $defs / SolidSpec / properties / profile / description

Previous value: -"Instead of `pts`: cross-section `[[u,z],…]` cm swept from `a` to `b`; u runs across the path (for a→b going down the plan, +u is +x), z is the height above the storey floor"New value: +"Instead of `pts`: cross-section `[[u,z],…]` cm swept from `a` to `b` (+u is +x when a→b goes down the plan; z above the floor)"

removedInput schema / $defs / WallPath / properties / closed / default
```
Removed value: -false
```
removedInput schema / properties / px / default
```
Removed value: -false
```

changedInput schema / properties / px / description

Previous value: -"Every point is given in pixels of the background image (converted with its scale and offset); lengths (t, h, off) stay in cm"New value: +"Points are background-image pixels; lengths stay in cm"

changedInput schema / properties / solids / description

Previous value: -"Solids from polygons: plan outlines raised by `h` (slabs, mezzanines, decks with any shape) or cross-sections swept from `a` to `b` (gables, ramps)"New value: +"Solids: plan outlines raised by `h` (slabs, decks) or cross-sections swept from `a` to `b` (gables, ramps)"

removedOutput schema / properties / ids / description
```
Removed value: -"Ids created or touched"
```
removedOutput schema / properties / ok / description
```
Removed value: -"Always true"
```
removedOutput schema / properties / rev / description
```
Removed value: -"Plan revision"
```
removedOutput schema / properties / text / description
```
Removed value: -"The reply as written"
```

removedOutput schema / properties / v / description

Removed value: -"Plan version written to, when there are several"

First observedv0.1.0Sep 24, 2026

TDQS

A3.7/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the atomicity trait (all primitives created in one step), which is genuinely useful, but says nothing about permissions, partial-failure behavior, or reversibility.

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 'Create' and packs all resource types into one dense sentence with no filler. It is long, but for a 10-parameter multi-primitive tool every clause carries information, so the length is defensible.

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?

Given the tool's breadth, the description enumerates all creatable primitives, and since an output schema exists it need not explain return values. The only gap is the absence of guidance on when to prefer it over sibling creation/edit tools.

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 every parameter and nested field is already documented in the schema. The inline hints (hs = height per point, at=[x,y], ceiling_flat=false follows wall profiles) largely restate schema content, so the description adds only marginal semantic value. Baseline 3 is correct.

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 the specific verb (Create) and enumerates every resource it produces: walls, rooms, dims, labels, roofs, solids. An agent can distinguish it from siblings like edit_walls or place without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The closing phrase 'in one atomic step' implies this is a batch-creation tool, which is useful context, but the description never names alternatives or states when-not-to-use it versus edit_walls, place, or move. Usage is only implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.