3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Change storeys

edit_levels

Destructive

Add, select, update, or delete building storeys in the active plan version; raise levels with their walls, floors, and openings, or mark traced plans as reference layers.

Instructions

Change the storeys. add {name?,h?,elev?} adds one on top (or at elev cm) and selects it; select {id}; delete {id} removes it and its content. update {id, elev?|h?|name?|reference?}: elev raises a storey with its walls, floors and openings (houses on stilts); reference=true marks it a tracing layer (imported plan, older version) that checks and ergonomics skip, which is what you want when two storeys share an elevation. Other tools act on the selected storey. Storeys belong to each plan version (variants): a change applies to the active one. The list is the levels tool.

Input Schema

Name	Required	Description
`h`	No	Storey height cm for `add` and `update`
`id`	No	Level id, e.g. `lv3`
`elev`	No	Floor elevation cm for `add` and `update` (e.g. a house on stilts)
`name`	No	Storey name for `add` and `update`
`action`	No	What to do with the storeys
`reference`	No	Mark the storey as a reference layer: a traced plan, a scan, an earlier version. Its content is drawing, not building, so layout checks and ergonomics leave it alone even when it sits at the same elevation as the storey being designed

Output Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv3.0.0Sep 30, 2026
- changedInput schema / properties / action / description
```
Previous value: -"`add`, `select`, `update` or `delete`"New value: +"What to do with the storeys"
```
- addedInput schema / properties / action / enum
```
Added value: +[
+  "add",
+  "select",
+  "update",
+  "delete"
+]
```
- 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.6/5.0

Behavior5/5

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

Beyond the destructiveHint annotation, the description discloses that delete removes the storey and its content, that elev raises a storey together with its walls, floors and openings, and that reference layers are skipped by checks and ergonomics. It also explains that changes apply to the active plan variant, which is important behavioral context not captured by 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 dense and front-loaded with the main purpose, then walks through each action. It is efficient, though the semicolon-heavy single paragraph is somewhat cramped for a mutation tool with four modes.

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?

For a destructive mutation tool with six optional parameters and an output schema, the description covers deletion consequences, elevation behavior with building content, reference-layer semantics, variant scoping, and the selected-storey workflow. Nothing essential for correct invocation is missing.

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 already 100%, so the schema fully documents parameters and baseline is 3. The description adds action-specific semantics: add places a storey on top or at elev, update with elev moves the whole storey, and reference=true marks a tracing layer. This meaningfully supplements the 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 states a specific verb and resource ('Change the storeys') and enumerates the exact sub-actions add/select/update/delete. It explicitly distinguishes this mutation tool from its sibling list tool with 'The list is the levels tool.'

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?

It explains the effect of each action and gives concrete usage scenarios such as using 'reference=true' when two storeys share an elevation, plus the workflow note that other tools act on the selected storey. It lacks explicit when-not-to-use guidance, but the context is otherwise clear.

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