3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Show the plan

show_plan

Read-only

Display a floor plan as an interactive viewer with pan, zoom, 3D view, and editor access, so users can see the drawing while you return 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. To look at the plan yourself use render_plan.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

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 declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds genuinely non-obvious behavior: the drawing is routed to the viewer and the agent only receives a one-line summary, which is important to know before calling. It does not describe what happens if the client cannot display a viewer, but that is a minor gap.

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 short, front-loaded sentences with zero waste. The primary purpose leads, followed by output behavior, then the sibling route.

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?

With an output schema present, return values need no further explanation, yet the description still clarifies that the reply is a one-line summary while the drawing goes to the viewer. Nothing an agent needs to call this correctly 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?

The tool takes zero parameters, so the baseline is 4 and there is nothing for the description to disambiguate. No parameter semantics are needed or missing.

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 (show the plan) plus the mechanism (interactive viewer with pan/zoom/3D/editor), and explicitly names the sibling it is not (render_plan). An agent can distinguish it from render_plan 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 both the condition ('where the chat client can display one') and the explicit alternative ('To look at the plan yourself use render_plan'). Routing between this tool and its sibling is unambiguous.

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