Skip to main content
Glama

Dump the Three.js scene graph with world-space data

inspect_scene

Retrieve detailed scene tree data (names, positions, rotations, bounding boxes, geometry, materials) from a Three.js HTML scene to diagnose placement and sizing errors.

Instructions

Returns the scene tree (names, types, positions, rotations, world bounding boxes, geometry and material info) for a scene that registers window.__scene. Use it to reason about EXACT placement and sizes when fixing issues reported by validate_scene (e.g. which Y puts the hat on the head). Three.js only.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
file_pathYesAbsolute path to the scene .html file (must register window.__scene)
max_depthNoMaximum tree depth to dump
filterNoOnly include subtrees whose name/type contains this substring
widthNoViewport width in px
heightNoViewport height in px
settle_framesNorequestAnimationFrame frames to wait after load before capturing
extra_wait_msNoExtra fixed wait after settling, for slow async scenes
timeout_msNoHard cap for the whole operation
Behavior3/5

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

No annotations provided, so description must carry the burden. It discloses the type of data returned and mentions parameters like settle_frames hinting at async behavior, but does not explicitly state that the tool is read-only or describe performance implications.

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 concise sentences with zero waste. The first states the action and output, the second gives usage context and a concrete example. Front-loads the key information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 8 parameters (1 required), no output schema, and no annotations, the description adequately explains the tool's purpose and hints at the output structure. Could mention the return format (e.g., JSON), but overall sufficient.

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

Parameters3/5

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

Schema description coverage is 100% with thorough parameter descriptions. The tool description does not add new semantics beyond what the schema already provides, so a baseline score of 3 is appropriate.

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?

Title and description clearly state the tool returns a Three.js scene graph with specific world-space data. The example 'which Y puts the hat on the head' and mention of validate_scene distinguish its purpose from sibling tools.

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?

Description explicitly guides the agent to use this tool to reason about exact placement/sizes when fixing issues from validate_scene. It does not explicitly state when not to use, but the context with sibling tools is clear enough.

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/eduardosm123/mcp-3d-llm'

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