3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Copy, align and group

arrange

Destructive

Manipulate multiple 3D elements in one undo step: align, distribute, array, flip, rotate, mirror, group, and reorder layers for precise floor plan layouts.

Instructions

Arrange elements in one undo step. array {ids,n,dx,dy,dz} adds n copies stepping by dx/dy/dz cm (rafters, columns); align {ids,axis,edge:low|middle|high,value} lines pieces up by an edge — backs on one line, fronts on another — instead of by centers you work out yourself; distribute {ids,axis,gap?} sets them side by side in the order given, from where the first one is (a run of joinery); flip {ids} turns a piece back to front, rebuilding what is inside it (mirror only swaps left and right and leaves the front where it was); rotate {ids,angle clockwise,about?,copy?}; mirror {ids,a,b,copy?} across the line a-b; group {ids,name?} joins pieces into one box that moves/hides together, ungroup {ids:[group]}; front/back {ids} draws rooms or pieces on top/underneath (pool over deck, rug under sofa). Returns new ids.

Input Schema

TableJSON Schema

Name	Required	Description
`a`	No	mirror: the first point of the mirror line
`b`	No	mirror: the second point of the mirror line
`n`	No	array: number of copies (default 1)
`dx`	No	array: step per copy along x, cm
`dy`	No	array: step per copy along y, cm
`dz`	No	array: step per copy upwards, cm (furniture and labels)
`gap`	No	distribute: centimeters between one piece and the next (default 0)
`ids`	Yes	The elements to act on (ungroup: the group)
`axis`	No	align/distribute: `x` or `y`
`copy`	No	rotate/mirror: keep the originals and transform a copy
`edge`	No	align: which edge to line up — `low` (left, or top of the plan), `middle`, `high`
`name`	No	group: its name
`about`	No	rotate: pivot `[x,y]` (default the center of the elements)
`angle`	No	rotate: clockwise degrees
`value`	No	align: the coordinate, cm, to put that edge on
`action`	Yes	What to do; `array` makes copies in a row

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.

Changed9 schema fields changedv3.0.0Sep 30, 2026

changedInput schema / $defs / Point2 / description

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

changedInput schema / properties / action / description

Previous value: -"`array` (copies in a row), `align`, `distribute`, `flip`, `rotate`, `mirror`, `group`, `ungroup`, `front`, `back`"New value: +"What to do; `array` makes copies in a row"

addedInput schema / properties / action / enum

Added value: +[
+  "array",
+  "align",
+  "distribute",
+  "flip",
+  "rotate",
+  "mirror",
+  "group",
+  "ungroup",
+  "front",
+  "back"
+]

removedInput schema / properties / copy / default
```
Removed value: -false
```
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

A4.3/5.0

Behavior4/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so mutation is covered. The description adds genuinely useful behavioral detail beyond that: the whole operation is "one undo step", group "moves/hides together", and flip "rebuilds what is inside it", which tells the agent about side effects.

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 core purpose, then a dense but waste-free clause per action. It is a long block, but every clause carries action-specific meaning; readability suffers slightly from being one unbroken paragraph.

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 10-action tool with 16 parameters, the description covers every action and notes the return ("Returns new ids"), and an output schema exists so return shape need not be explained. It is nearly complete, lacking only positioning relative to sibling tools.

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?

With 100% schema coverage the baseline is 3, but the description adds real value by mapping parameters to actions (array {ids,n,dx,dy,dz}, align {ids,axis,edge,value}, distribute {ids,axis,gap?}), which the flat schema does not make explicit. This disambiguates the 16 shared parameters per action.

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 operation type ("Arrange elements in one undo step") and then enumerates all ten actions with concrete domains (rafters, columns, joinery, pool over deck). An agent can tell this apart from siblings like move/place/joinery because the description makes clear it is the multi-action transform/grouping toolbox.

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?

Supplies per-action usage context, e.g. align instead of "centers you work out yourself", flip vs mirror ("mirror only swaps left and right"), and distribute for "a run of joinery". It does not, however, state when to reach for this tool over sibling tools such as move or place.

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