3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Change plan versions

edit_variants

Destructive

Manage floor plan versions: duplicate the active version, create an empty one, switch, rename, or delete variants; edits apply to the active version.

Instructions

Change the plan versions (tabs): duplicate {name?} copies the active one, new {name?} starts an empty one — both switch to it; switch {i}; rename {i,name}; delete {i}. Edits apply to the active version. The list is the variants tool.

Input Schema

TableJSON Schema

Name	Required	Description
`i`	No	Variant index for switch/rename/delete
`name`	No	Name for duplicate/new/rename
`action`	No	`duplicate` copies the active version, `new` starts an empty one

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

Changed8 schema fields changedv3.0.0Sep 30, 2026

changedInput schema / properties / action / description

Previous value: -"`duplicate` (copy active), `new` (empty), `switch`, `rename` or `delete`"New value: +"`duplicate` copies the active version, `new` starts an empty one"

addedInput schema / properties / action / enum

Added value: +[
+  "duplicate",
+  "new",
+  "switch",
+  "rename",
+  "delete"
+]

removedOutput schema / properties / i / description
```
Removed value: -"Index of the new version"
```
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 the safety profile is covered; the description still adds real context beyond them, notably that duplicate/new both auto-switch to the new version and that subsequent edits apply to the active version. It does not say whether delete is recoverable or what happens to the remaining versions.

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, then enumerates actions in a compact per-action notation with no wasted sentences. The brace shorthand ({name?}, {i}) is terse to the point of being slightly cryptic, but it keeps the definition short and scannable.

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 five enum actions, the active-version behavior, and points to the list tool, and an output schema exists so return values need no explanation. A mutation with destructiveHint=true could still note permission requirements or irreversibility of delete, but 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 baseline is 3, but the description adds value the schema lacks: it binds each parameter to specific actions (i only for switch/rename/delete, name for duplicate/new/rename). Since all three params are optional, this action-to-argument mapping is the main thing preventing mis-invocation.

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 and resource ('Change the plan versions (tabs)') and immediately disambiguates against the sibling 'variants' tool ('The list is the variants tool'). An agent can tell this is the mutation counterpart to variants without opening either 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?

Maps each action to its effect and required argument (duplicate {name?}, new {name?}, switch {i}, rename {i,name}, delete {i}), which tells the agent which call shape to pick. It also routes listing to the 'variants' sibling. It stops short of explicit when-not-to-use or precondition guidance (e.g. whether delete requires confirmation).

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