3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Show the plan

show_plan

Read-only

Display floor plans in an interactive viewer with pan, zoom, 3D view, and editor access. Sends the drawing to the viewer and returns a one-line summary.

Instructions

Show the plan to the user as an interactive viewer (pan, zoom, 3D view, open in the editor) where the chat client can display one. Reply: a one-line summary for you; the drawing goes to the viewer (none to a client without one). To look at the plan yourself use render_plan.

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`svg`	No
`name`	Yes
`editor`	Yes
`summary`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv3.2.0Oct 28, 2026

changedOutput schema / required

Previous value: -[
-  "name",
-  "svg",
-  "summary",
-  "editor"
-]New value: +[
+  "name",
+  "summary",
+  "editor"
+]

Changed4 schema fields changedv3.0.0Sep 30, 2026
- removedOutput schema / properties / editor / description
```
Removed value: -"Link that opens the project in the editor"
```
- removedOutput schema / properties / name / description
```
Removed value: -"Project name"
```
- removedOutput schema / properties / summary / description
```
Removed value: -"{rooms, area, walls, pieces}"
```
- removedOutput schema / properties / svg / description
```
Removed value: -"The plan as SVG"
```
First observedv0.1.0Sep 24, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already cover safety (readOnlyHint=true, openWorldHint=false), yet the description adds real behavior: the artifact is delivered to a viewer rather than the response, the response is only a one-line summary, and there is a documented degradation path for clients without a viewer. It stops short of saying what happens on repeated calls or whether an existing viewer is replaced, which keeps it off a 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three dense sentences, front-loaded with what the agent gets, followed by the response contract and the alternative tool. Every clause carries information an agent would otherwise have to guess.

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 zero-parameter display tool with an output schema, the description supplies exactly the missing behavioral context: where the drawing goes, what comes back, and the no-viewer case. Nothing needed to invoke it correctly is absent.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description does not introduce any param-like configuration that the schema would need to back.

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?

Specific verb+resource ("Show the plan ... as an interactive viewer") with the rendering modes enumerated (pan, zoom, 3D view, open in the editor). It explicitly separates itself from the similarly named render_plan, so an agent can choose 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 Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives a use condition ("where the chat client can display one") and names the alternative with its triggering condition ("To look at the plan yourself use render_plan"). No inference about when to pick which is required.

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