3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Move elements

move

Destructive

Relocate selected furniture, walls, or labels in a floor plan by specifying a shift in centimeters or a target coordinate, with an option to preview changes before 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
`v`	No	Plan version written to, when there are several
`ok`	No	Always true
`dry`	No	Nothing was written
`ids`	No	Ids created or touched
`rev`	No	Plan revision
`gone`	No	Ids removed, or their count
`text`	No	The reply as written
`added`	No	Ids added, or their count
`score`	No	Score [before, after]
`changed`	No	{id, from, to} per element changed; a count past 20
`resolved`	No	Findings settled
`clearances`	No	Free floor around touched pieces, by id
`issues_new`	No	Layout issues created
`properties`	No	Project properties changed
`added_count`	No	Roots added
`annotations`	No	Annotation switches {from, to}
`score_scope`	No	Disciplines scored
`new_findings`	No	Findings created
`changed_count`	No	Roots changed
`issues_changed`	No	Layout issues resized
`issues_resolved`	No	Layout issues settled
`findings_changed`	No	Findings changed
`acceptance_cleanup`	No	Acceptances orphaned, and the calls that clear them

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, so mutation is known. The description adds value by explaining the dry run mechanism (true vs 'summary') and that it writes only when not dry, which is beyond what annotations provide. No contradiction with 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 description is concise, a single sentence that front-loads the core action and parameter modes, then mentions dry run and a reference to 'update'. No unnecessary fluff; it earns its length. Could slightly improve by separating dry run into a clearer clause, but overall efficient.

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, the return format is covered elsewhere. The description covers the main behavior, dry run semantics, and parameter relationships, which is sufficient for an agent to call the tool correctly. It does not cover edge cases like 'joined' but that is in the schema.

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 description coverage is 100%, so all parameters are documented. The description adds semantics by clarifying the relationship between dx/dy and 'to' (alternatives), the behavior of 'ids' (first moves, rest keep offsets), and the meaning of dry run values, enhancing understanding beyond the raw schema.

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?

The description clearly states the tool moves elements, specifying two modes (dx/dy and to), and clarifies that the first id goes to the destination while others keep offsets. This distinguishes it from siblings like 'place' and 'arrange' by explicitly naming the operation and its key behavior.

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 description explains how the tool works (e.g., dry run modes, first id behavior) but does not explicitly state when to use it versus alternatives or when not to use it. It references 'update' for dry run details but lacks clear usage boundaries, leaving the agent to infer typical use cases.

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