3D New Era AI

Overview Schema Source Related Servers Discussions Admin

Render a 3D view

render_3d

Read-only

Generates 3D views of a home design from a floor plan, including elevations, aerial angles, and cutaway sections. Adjust view, camera, and walls to inspect interior layout.

Instructions

PNG of the home in 3D (software render with outlines, no GPU needed). view: front|back|left|right|top orthographic elevations — front looks from the plan's bottom edge (large y) toward y=0, back from y=0 toward large y, left from x=0, right from large x; cut=cm makes a section keeping only what is beyond that plane from the viewer (front cut=200 keeps y<200, so the wall at y=0 stays as the backdrop; to remove it look from back), aerial (default; frames the whole building; yaw degrees: 0 from east/+x, 90 from south/plan bottom (default 60); pitch down; zoom >1 farther), visitor (current visitor camera) or cam=i (stored point of view). walls=cutaway drops the walls between the eye and a room to 40 cm, walls=down drops them all; either hides ceilings, roofs and the doors, windows and wall pieces of lowered walls, to see the furniture from the side. Keep w/h small.

Input Schema

TableJSON Schema

Name	Required	Description
`h`	No	Height px (default 360, 64..1200)
`w`	No	Width px (default 480, 64..1600)
`cam`	No	Stored point of view index (see cameras)
`cut`	No	Elevations: section plane in plan cm (y for front/back, x for left/right, height for top); what lies between the viewer and it is cut away — walls and pieces alike. front views from large y, back from y=0
`yaw`	No	Aerial turn, degrees
`view`	No	`aerial` (default) or `visitor`
`zoom`	No	Aerial distance factor: 1 frames the building, 2 twice as far
`pitch`	No	Aerial height angle, degrees
`walls`	No	`up` (default), `cutaway` or `down`

Output Schema

TableJSON Schema

Name	Required	Description	Default
`mimeType`	Yes	Type of the image in the content (image/png)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 24, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnlyHint annotation, the description discloses concrete render behavior: software-only rendering with outlines, no GPU requirement, the effects of walls=cutaway/down on visibility, and a performance caution in 'Keep w/h small'. These are non-obvious behaviors an agent could not infer from annotations or schema alone.

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?

The description is dense but every clause carries necessary information; there is no filler. It front-loads the core purpose and render type, then systematically covers each view mode. The semicolon-heavy style is hard to skim, but it is concise relative to the amount of behavioral semantics conveyed.

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 9 optional parameters, complex coordinate rules, and wall-cutaway behavior, the description covers all modes and their interactions, including defaults and how to remove a backdrop wall. The output schema covers the return format, and the readOnlyHint covers safety, so nothing necessary for correct invocation is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description substantially enriches parameter meaning with coordinate orientation, defaults, and edge cases: 'front looks from the plan's bottom edge (large y) toward y=0', 'front cut=200 keeps y<200', 'yaw degrees: 0 from east/+x', and zoom semantics. This goes far beyond the schema's terse property descriptions.

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?

The description opens with a specific verb and resource: 'PNG of the home in 3D (software render with outlines, no GPU needed)'. It clearly distinguishes a 3D render from 2D plan/photo siblings and enumerates exact view modes, so an agent knows precisely what the tool produces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description gives extensive context for choosing view modes, cut planes, and wall treatments, including defaults like 'aerial (default)' and 'visitor'. However, it never names alternatives such as render_photo or render_plan, nor does it state when to prefer this tool over those siblings, leaving the tool-vs-alternative decision implied rather than explicit.

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