3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Show the plan

show_plan

Read-only

Display the plan in an interactive viewer for direct pan, zoom, and 3D exploration, and open it in the editor; returns a one-line summary while the drawing is shown to the user.

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
`svg`	Yes	The plan as SVG
`name`	Yes	Project name
`editor`	Yes	Link that opens the project in the editor
`summary`	Yes	{rooms, area, walls, pieces}

Schema Changelog

Changes observed during successful MCP inspections.

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 declare readOnlyHint=true, so the safety profile is covered. The description adds the behavioral detail that the agent receives a one-line summary while the drawing goes to a viewer, and describes the viewer's interactive features. This goes beyond the annotation without contradicting it.

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?

Two sentences with no filler. The primary purpose is front-loaded, and the reply format and alternative tool are stated in the second sentence. Every word earns its place.

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?

A zero-parameter tool with an output schema and read-only annotation. The description covers the purpose, the viewer behavior, and the distinction from render_plan. Nothing an agent needs to call it 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 has zero parameters, so the baseline for parameter semantics is 4. The description correctly notes there are no inputs, and no parameter meaning is needed beyond what the empty schema implies.

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 (show) and resource (the plan) plus the exact presentation format (interactive viewer with pan, zoom, 3D view, open in editor). It explicitly contrasts with render_plan, so the agent can tell them apart without opening any 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?

Explicitly names the alternative render_plan and the condition that selects it ('To look at the plan yourself use render_plan'). This clearly communicates when this tool is for the user and when the other is for the agent's own inspection.

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