3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Place furniture, doors and windows

place

Add catalog furniture, doors and windows to a floor plan, snap them to walls, set facing, copy existing pieces, and dry-run clearances before applying.

Instructions

Place catalog items, or copy= of a piece already in the project (model, finish and parts; catalog scope=project lists them). at=[x,y] is the center (doors and windows near a wall snap into it; into=[x,y] picks the swing side); wall= (+along cm) puts doors and windows in a wall, or furniture with its back to it. facing=+x|-x|+y|-y|[x,y]| turns the front toward a side, point or element, preferred to angle (clockwise degrees, y down: 0 front to +y, 90 to -x, 180 to -y, 270 to +x); a piece whose back belongs on a wall, put within 30 cm of one with neither, turns its back to it. The reply says where fronts ended: faces=f3:+y(seat), turned=f3:back to w2. Ceiling pieces hang from the ceiling the 3D draws and follow it: a pendant takes elev (shade bottom, ~150-160 over a table) or h (drop). w/d/h, pitch/roll, mat, opacity; defaults {…} fills every item; px=true reads background pixels. cat=beam with a,b=[x,y,z] makes rafters and posts. dry=true answers what it would add, the clearances and the findings, without writing.

Input Schema

Name	Required	Description
`v`	No	`variants` index, 0-based (not a revision); made active
`px`	No	Coordinates (`at`, `into`, `a`, `b`, `along`) are pixels of the background image
`dry`	No	Try it without applying; see `update`. `"summary"` answers short
`items`	Yes	The pieces to place, one object each: `id` from the catalog (or `copy`), and where (`at`, or `wall` + `along`)
`defaults`	No	Fields every item takes unless it sets them (cat, w, d, h, color, mat…)

Output Schema

Name	Required	Description	Default
`v`	No
`ok`	No
`dry`	No
`ids`	No
`rev`	No
`gone`	No
`text`	No
`added`	No
`faces`	No
`score`	No
`turned`	No
`changed`	No
`resolved`	No
`clearances`	No
`issues_new`	No
`properties`	No
`added_count`	No
`annotations`	No
`score_scope`	No
`new_findings`	No
`changed_count`	No
`issues_changed`	No
`issues_resolved`	No
`findings_changed`	No
`acceptance_cleanup`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv3.2.0Oct 28, 2026

changedInput schema / $defs / Dry / description

Previous value: -"How much of a dry run to answer with: `true` everything it would change, `\"summary\"` the decision — pieces moved, roots, clearances, findings, score"New value: +"How much of a dry run to answer: `true` everything it would change, `\"summary\"` the decision — pieces moved, roots, clearances, findings, score"

changedInput schema / $defs / PlaceSpec / properties / along / description

Previous value: -"Distance along the wall from its start, cm (default: middle)"New value: +"Distance along the wall from its start, cm (default: `at`'s, or middle)"

changedInput schema / $defs / PlaceSpec / properties / at / description

Previous value: -"Center on the plan. Optional when `wall` is given; a door or window placed `at` a point near a wall snaps into it"New value: +"Center on the plan, optional with `wall`; a door or window `at` a point near a wall snaps into it"

changedInput schema / $defs / PlaceSpec / properties / glass / description

Previous value: -"Glass of a guard or a balcony closure: `laminated`, `tempered`, `tempered-laminated` or `wired`"New value: +"Glass of a guard or a balcony closure"

addedInput schema / $defs / PlaceSpec / properties / glass / enum

Added value: +[
+  "laminated",
+  "tempered",
+  "tempered-laminated",
+  "wired"
+]

changedInput schema / properties / v / description

Previous value: -"Plan version (tab) to write to; switches to it first"New value: +"`variants` index, 0-based (not a revision); made active"

Changed32 schema fields changedv3.0.0Sep 30, 2026

changedInput schema / $defs / Dry / description

Previous value: -"Runs an edit against a copy of the plan and reports what it would do. Trying a size used to mean applying it, reviewing, and undoing — a round trip that showed in the user's window and burned a revision each time. The copy has no history and is thrown away, so nothing of that happens. How much of a dry run to answer with. `true` answers with everything it would change; `\"summary\"` answers with the decision — how many pieces move, which roots, the clearances, the findings and the score — because a group that rebuilds lists ninety-seven parts for a choice that fits in five lines"New value: +"How much of a dry run to answer with: `true` everything it would change, `\"summary\"` the decision — pieces moved, roots, clearances, findings, score"

changedInput schema / $defs / LightSpec / properties / z / description

Previous value: -"Source height as a fraction of the piece's height (default: its base for spots and panels, the middle otherwise)"New value: +"Source height, fraction of the piece's (default: base for spots and panels, else middle)"

removedInput schema / $defs / PlaceSpec / properties / cat / default
```
Removed value: -""
```

addedInput schema / $defs / PlaceSpec / properties / stretch

Added value: +{
+  "description": "With `model`: w/d/h may stretch it unevenly; otherwise one or two of them scale it evenly",
+  "type": "boolean"
+}

addedInput schema / $defs / PlaceSpec / properties / unit

Added value: +{
+  "description": "With `model`: unit of its numbers, `m`, `cm`, `mm` or `in` (default: guessed from its size)",
+  "type": "string"
+}

changedInput schema / $defs / Point2 / description

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

removedInput schema / properties / px / default
```
Removed value: -false
```

removedOutput schema / properties / acceptance_cleanup / description

Removed value: -"Acceptances orphaned, and the calls that clear them"

removedOutput schema / properties / added / description
```
Removed value: -"Ids added, or their count"
```
removedOutput schema / properties / added_count / description
```
Removed value: -"Roots added"
```
removedOutput schema / properties / annotations / description
```
Removed value: -"Annotation switches {from, to}"
```

removedOutput schema / properties / changed / description

Removed value: -"{id, from, to} per element changed; a count past 20"

removedOutput schema / properties / changed_count / description
```
Removed value: -"Roots changed"
```

removedOutput schema / properties / clearances / description

Removed value: -"Free floor around touched pieces, by id"

removedOutput schema / properties / dry / description
```
Removed value: -"Nothing was written"
```

removedOutput schema / properties / faces / description

Removed value: -"Where each front looks: <id>:<side>(<front>)"

removedOutput schema / properties / findings_changed / description
```
Removed value: -"Findings changed"
```
removedOutput schema / properties / gone / description
```
Removed value: -"Ids removed, or their count"
```
removedOutput schema / properties / ids / description
```
Removed value: -"Ids created or touched"
```
removedOutput schema / properties / issues_changed / description
```
Removed value: -"Layout issues resized"
```
removedOutput schema / properties / issues_new / description
```
Removed value: -"Layout issues created"
```
removedOutput schema / properties / issues_resolved / description
```
Removed value: -"Layout issues settled"
```
removedOutput schema / properties / new_findings / description
```
Removed value: -"Findings created"
```
removedOutput schema / properties / ok / description
```
Removed value: -"Always true"
```
removedOutput schema / properties / properties / description
```
Removed value: -"Project properties changed"
```
removedOutput schema / properties / resolved / description
```
Removed value: -"Findings settled"
```
removedOutput schema / properties / rev / description
```
Removed value: -"Plan revision"
```
removedOutput schema / properties / score / description
```
Removed value: -"Score [before, after]"
```
removedOutput schema / properties / score_scope / description
```
Removed value: -"Disciplines scored"
```
removedOutput schema / properties / text / description
```
Removed value: -"The reply as written"
```

removedOutput schema / properties / turned / description

Removed value: -"Pieces turned back to a wall: <id>:back to <wall>"

removedOutput schema / properties / v / description

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

First observedv0.1.0Sep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare this is a non-read-only, non-destructive, closed-world mutation. The description adds substantial behavioral context: snapping into walls, door swing side via `into`, default back-to-wall orientation, ceiling-following fixtures, reported front directions, and dry-run output. Nothing contradicts the annotations.

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?

The opening sentence front-loads the primary operation, and most clauses carry real information. However, the paragraph is extremely dense and semicolon-heavy, and some details would be easier to scan as structured bullets or shorter sentences.

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?

Given the complex schema, annotations, and output schema, the description covers placement modes, orientation rules, wall/ceiling behavior, dry runs, and return-value hints. An agent has enough information to invoke the tool correctly without needing additional undocumented context.

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. The description still adds meaningful semantics beyond the schema: `facing` is preferred over `angle`, pieces with a back within 30 cm of a wall turn automatically, `defaults` fills every item, and `cat=beam` uses `a`/`b` endpoints for rafters and posts.

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: placing catalog items, copying existing pieces, or creating beams. It explicitly distinguishes `cat` from `copy` and points to the `catalog` tool for listing project pieces, so an agent can identify the core operation without opening the schema.

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

Usage Guidelines4/5

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

Explains when to use `copy` instead of `cat`, when `at` versus `wall`/`along` applies, when `facing` is preferable to `angle`, and what `dry=true` does. It does not explicitly contrast this tool with siblings like `move`, `create`, or `update`, so usage guidance is clear but not fully exhaustive.

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