Send scene.inspect to the active Harness session. Report object names and types, collections,
active camera, frame range, materials, lights, missing assets, warnings, and sceneRevision.
Do not use mutating operators during inspection. If Blender changed outside Codex, re-inspect instead of guessing and use the new revision for subsequent commands.
When to Use
Use before any design, modification, preview, restore, or export begins, and when external modifications, revision conflicts, or unknown scene state are detected.
Prerequisites
- A discoverable and authorized Harness session; inspection behavior must be read-only.
- Clear scope of focus for this task, such as objects, collections, cameras, materials, frame range, or missing assets.
Workflow
Step 1. Read the session state and the current sceneRevision.
Step 2. Call scene.inspect, collect objects, collections, cameras, materials, lights, timeline, and warnings.
Step 3. Perform a focused inspection of task-relevant objects, without performing any fixes or selection changes.
Step 4. Output facts, unknowns, and the suggested next domain skill, bound to this revision number.
Validation and Delivery Evidence (Validation)
Retain the inspection time, session ID, scene revision, object statistics, active camera, frame interval, missing assets, and warnings. Subsequent commands must reference the same or an updated revision number.
Rules and Capability Boundaries (Inapplicable Scenarios)
Inspection does not modify the scene, does not infer hidden intent, and does not equate object existence with quality passing. Report problems only, unless the user separately authorizes a fix.
Gotchas (Common Issues and Recovery)
- Revision number changed: discard old assumptions and re-inspect.
- Session unreachable: go to
blender-mcp-setup, and do not fabricate a manifest. - Output too large: focus on task objects, but retain global warnings and revision evidence.