Skip to main content
Glama

FilmLab

by com.thefilmradar
OverviewDiscussionsAdmin

Reconstruct Location in 3D

lab_location_recon

Reconstruct a real place in 3D from a scan clip: keyframes are pulled from the clip server-side and turned into a point cloud / splat on the location board, so a scouted room can be looked at from angles nobody filmed. THE SCAN IS NOT MADE HERE — it is a walk-around clip uploaded by the FilmLab camera app together with the phone's lens data. This tool takes one that already exists; lab_list_location_scans gives you the ids. SLOW AND NOT A JOB ROW: the answer comes back as 'reconstructing', and the finished state is picked up ONLY by lab_list_location_scans — lab_job_status and lab_get_job will never show this one finish. If the call times out, the reconstruction normally keeps running on the server: list the scans instead of firing it again. Re-running is allowed from any state that is not done.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
engineNoWhich reconstruction path. Omit for the backend default. 'vggt' is scene-scale and fast but gives a point cloud; 'vggt-splat' trains a walkable Gaussian splat from the same scan (minutes on a GPU, not seconds). Both need their own model configured on the backend — where it is not, the answer says so instead of falling back silently.
image_idYesId of the SCAN row (from lab_list_location_scans) — positive integer as string. It is a row in the image gallery whose tool is the location scanner; a normal generated image with that id is rejected, not reconstructed.
max_photosNoHow many keyframes are pulled from the clip and handed to the reconstruction. Omit to let the engine use its own count — more frames mean a wider parallax baseline and a slower run.
project_idYesProject id (from lab_list_projects) — positive integer as string. The scan must belong to it; a scan of another project is not found rather than borrowed.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / engine / description
      Previous value: -"Which reconstruction path. Omit for the backend default. The second path is scene-scale and needs its model configured on the backend — where it is not, the answer says so instead of falling back silently."New value: +"Which reconstruction path. Omit for the backend default. 'vggt' is scene-scale and fast but gives a point cloud; 'vggt-splat' trains a walkable Gaussian splat from the same scan (minutes on a GPU, not seconds). Both need their own model configured on the backend — where it is not, the answer says so instead of falling back silently."
    • changedInput schema / properties / engine / enum
      Previous value: -[
-  "fal-sam3d",
-  "vggt"
-]New value: +[
+  "fal-sam3d",
+  "vggt",
+  "vggt-splat"
+]
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. First observed

TDQS

A4.7/5.0
Behavior5/5

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

With annotations only marking it as non-readOnly and non-destructive, the description adds critical behavioral context: the tool is slow, returns 'reconstructing', its completion is visible ONLY through lab_list_location_scans, and lab_job_status/lab_get_job will never show it finishing. It also discloses timeout behavior and re-run semantics, which go well beyond the annotations.

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 front-loaded with the core action, then layers critical caveats in a logical order: source of the scan, job tracking, timeout handling, and re-run rules. Every sentence adds distinct value, and the use of caps for key warnings makes important constraints scannable without waste.

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 as an asynchronous 3D reconstruction and the absence of an output schema, the description is complete: it explains the input source, the slow/async nature, where completion is observed, timeout behavior, and re-run limits. The rich schema and annotations cover the rest.

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%, so all four parameters are already richly documented in the input schema. The description does not add parameter-specific syntax or format details beyond what the schema provides; it only implies that image_id is a scan row. The baseline of 3 is appropriate when the schema carries the full semantic load.

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: 'Reconstruct a real place in 3D from a scan clip.' It explicitly distinguishes this tool from related operations by stating 'THE SCAN IS NOT MADE HERE' and naming the source of ids (lab_list_location_scans). An agent can easily tell it apart from siblings like lab_analyze_location_image or lab_depth_map.

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

Usage Guidelines5/5

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

The description gives clear when-to-use guidance: it takes an existing scan, ids come from lab_list_location_scans, and re-running is allowed from any state that is not done. It also explicitly tells the agent what to do on timeout — list the scans instead of firing again — and notes that job status tools will never show completion. These are precise alternatives and conditions.

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

All FilmLab toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources