3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Move elements

move

Destructive

Reposition floor-plan elements by dx/dy cm or to an [x,y] point; the first ID anchors while others keep offsets. Use a dry run to preview changes without applying.

Instructions

Move elements by dx,dy cm, or to=[x,y]: the first id (a piece or a label) goes there and the rest keep their offsets. dry=true answers what it would do without writing anything, dry="summary" answers it short; see update.

Input Schema

TableJSON Schema

Name	Required	Description
`dx`	No	Shift in x, cm (with `dy`)
`dy`	No	Shift in y, cm (with `dx`)
`to`	No	Instead of dx/dy: where the first id goes, [x,y] as reads give it (a piece's or a label's center); the others keep their offsets
`dry`	No	Try it without applying; see `update`
`ids`	Yes	The elements to move together
`joined`	No	Drag endpoints of walls joined to moved walls (default true)

Output Schema

TableJSON Schema

Name	Required	Description	Default
`v`	No
`ok`	No
`dry`	No
`ids`	No
`rev`	No
`gone`	No
`text`	No
`added`	No
`score`	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.

Changed25 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 / Point2 / description

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

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 / 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 / v / description

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

First observedv0.1.0Sep 24, 2026

TDQS

B3.2/5.0

Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds the dry-run behavior ('answers what it would do without writing anything'), which is genuinely useful, but it largely restates what the schema already documents for the `dry` param and omits any undo/reversibility or permission context for a destructive mutation.

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 purpose and both move modes are front-loaded, and there is no filler. It is slightly dense/run-on with the tail-end cross-reference, but every clause carries information.

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?

With an output schema present, return format need not be explained, and the description covers the two movement modes and dry-run options. For a destructive operation it stops short of stating reversibility or permission requirements, leaving a minor gap.

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 the baseline is 3. The description repeats the dx/dy cm units, the to=[x,y] semantics, and the dry modes — helpful phrasing, but no syntax, units, or edge-case meaning beyond what the schema already supplies.

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 (Move) and resource (elements) and details two modes: dx/dy offsets in cm, or to=[x,y] with the first id going there. It is clearly distinguishable in concept, but never names the overlapping siblings (arrange, place, update) it should be chosen over.

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

Usage Guidelines2/5

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

The only usage signal is the trailing 'see `update`' cross-reference and the dry-run explanation, both tied to a parameter rather than to tool selection. There is no statement of when to use move vs arrange/place, nor any prerequisite or when-not guidance.

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