3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Change storeys

edit_levels

Destructive

Add, select, update, or delete storeys in a floor plan, set height and elevation, and designate a level as a reference layer for imported plans.

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	`add`, `select`, `update` or `delete`
`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
`v`	No	Plan version written to, when there are several
`ok`	Yes	Always true
`ids`	No	Ids created or touched
`rev`	No	Plan revision
`text`	Yes	The reply as written

Schema Changelog

Changes observed during successful MCP inspections.

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?

Discloses side effects beyond the destructiveHint annotation: delete removes content, add selects the new storey, update with elev raises walls/floors/openings, and reference layers are skipped by checks and ergonomics. This adds meaningful behavioral context beyond the simple mutation flag.

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?

Compact and dense, front-loading the purpose and then covering each operation in a single line. The reference explanation is slightly verbose but directly useful. No filler or redundant phrasing.

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?

Covers all four actions and all six parameters, explains the selection side effect, and points to the levels tool for listing. With an output schema present, it provides sufficient context for correct invocation without needing to describe return values.

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?

Though the schema documents all parameters at 100%, the description adds action-dependent semantics: add takes name?/h?/elev? and selects; update takes id plus optional elev/h/name/reference with specific behaviors for each. This clarifies parameter combination per action, which the schema alone does not.

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 verb 'Change' and resource 'storeys', then enumerates four distinct operations (add, select, delete, update) with their parameter patterns. It explicitly differentiates from the sibling 'levels' tool by saying 'The list is the levels tool,' making the purpose unambiguous.

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?

Provides clear context on selection: 'Other tools act on the selected storey.' Also explains when to use the reference flag: 'which is what you want when two storeys share an elevation.' Points to levels for listing. Does not explicitly exclude alternatives but gives situational guidance for the key decisions.

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