3D New Era AI

by leandrodaf

Overview Schema Source Related Servers Discussions Admin

Rust

Hybrid

Change storeys

edit_levels

Destructive

Add, select, update, or delete storeys; raise elevations for houses on stilts and mark tracing layers to skip checks.

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. The list is the levels tool.

Input Schema

TableJSON 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

TableJSON 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?

Goes well beyond the annotations: delete removes a storey *and its content*, elev raises a storey *with its walls, floors and openings*, reference=true marks a tracing layer that *checks and ergonomics skip*. These are meaningful mutation consequences and side effects an agent needs, consistent with destructiveHint=true.

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-loads the purpose ('Change the storeys') then walks through actions compactly with shorthand notation. Every clause carries information; the brace notation is terse but not padded, though slightly cryptic to parse.

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 6-parameter mutation tool with an output schema, the description covers all actions, their parameters, destructive side effects, the reference-layer behavior, and the sibling listing tool. 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 100%, so the baseline is 3, but the description adds real value by mapping which parameters apply to which action (name/h/elev for add; id+elev/h/name/reference for update) and explaining the semantic effect of elev and reference. Adds meaning beyond the field descriptions alone.

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+resource (changing storeys) and then enumerates the four operations (add, select, delete, update) with their effects. It also clearly differentiates from the sibling `levels` tool by naming it as the list operation. An agent can distinguish this from other edit_* tools 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 each action applies (e.g. use `reference=true` when two storeys share an elevation) and routes listing to the `levels` tool. It notes 'Other tools act on the selected storey,' implying selection is a prerequisite. No explicit when-not guidance against other edit tools, but context is clear.

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