get_scene_screenshot

info.3dcms/mcp · Verify this server

Render the scene server-side (real WebGL, headless) and return screenshot image(s) — your EYES on the scene. Use it after apply_ops batches: judge the image (floating objects, unreadable/overlapping text, empty horizon, bad spacing, wrong colors) and fix with apply_ops. Discipline: at most 2 screenshot→fix rounds per user request, then report what you built. views (max 4, default = the visitor's entry view): pass "page:<pageIdOrSlug>" to frame one page/neighborhood, or {position:[x,y,z], target:[x,y,z], fov?} for an exact camera. Rendering is real but slow — ~10s for simple scenes, up to ~2 minutes for asset-heavy ones (repeat shots of an unchanged scene are cached and instant). Rate-limited: prefer ONE well-chosen view; only multi-view when areas are far apart. If it returns a busy/unavailable error, keep building and retry once later — do not loop on it.