Skip to main content
Glama

Multipass 3D scene (SSAO + depth)

multipass_3d_depth

Build a 3D scene with SSAO and a depth map output. Expose the depth buffer for synthetic depth effects without a depth camera.

Instructions

Build a renderable 3D scene with depth cues that read on stage: a Geometry COMP holding the chosen primitive (sphere/box/torus/grid), a Camera, a Light, and a Render TOP beauty pass, output as a Null — like create_3d_scene but with an optional Screen-Space Ambient Occlusion (SSAO) pass for contact shadows, and an optional Depth TOP output. The SSAO TOP is wired directly after the Render TOP (it needs the depth buffer — no TOP between them) and combined with the color. When expose_depth is on, a Depth TOP resolves the same render into a depth map exposed as a second Null ('depth_out'); feed that path into create_depth_displacement or create_depth_silhouette with source='existing_top' for a synthetic depth-driven effect — no depth camera needed. Optionally GPU-instanced into a grid, with spin over time. Exposes Spin, Zoom, and (with SSAO) an Ssao toggle. Returns a summary plus a JSON block with the container path, created node paths, the render/output/depth paths, exposed controls, node errors, warnings, and an inline preview image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameNoName of the self-contained container created under parent_path.multipass_3d
parent_pathNoParent COMP path the multipass 3D container is created inside (default '/project1')./project1
geometryNoPrimitive to render.torus
instancesNoGPU-instanced copies scattered over a grid (1 = single).
ssaoNoAdd a Screen-Space Ambient Occlusion pass for contact shadows/depth.
expose_depthNoExpose a Depth TOP output (feeds create_depth_displacement/silhouette synthetically).
spinNoDegrees/sec rotation.
resolutionNoRender resolution [width, height] in pixels.
Behavior5/5

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

The description adds substantial behavioral context beyond annotations, such as the wiring constraint (SSAO TOP directly after Render TOP), exposure of controls (Spin, Zoom, SSAO toggle), and return format. It does not contradict the annotations (readOnlyHint: false, destructiveHint: false, openWorldHint: true).

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?

The description is detailed but stays focused, front-loading the main purpose and then adding necessary details. While not ultra-concise, every sentence adds value and avoids redundancy.

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?

Given the tool's complexity (8 parameters, no output schema), the description covers all essential aspects: generated nodes, constraints, controls, and how to use the outputs. It is complete enough for an agent to invoke correctly.

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?

With 100% schema coverage, the description adds meaning beyond the schema by explaining how parameters affect behavior, e.g., the SSAO wiring requirement, that expose_depth enables feeding depth to other tools, and the default values and ranges. This enriches the agent's understanding.

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 clearly states the tool builds a renderable 3D scene with depth cues, including optional SSAO and depth output. It distinguishes itself from the sibling tool 'create_3d_scene' by explicitly noting the additional SSAO and depth passes.

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?

The description provides guidance by comparing to 'create_3d_scene' and specifying when to choose this tool (for SSAO and depth). It also advises feeding the depth output into create_depth_displacement or create_depth_silhouette. However, it lacks explicit 'when not to use' guidance.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Pantani/tdmcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server