- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
SpaceMCP is a training-free framework that exposes reconstructed 3D scenes through a reusable interface for spatial reasoning. It combines metric reconstruction, language-guided segmentation, and geometric queries, allowing a model to plan tool calls and answer using the returned information. The paper evaluates the framework across nine backbones and three benchmarks.
Critical strengths
-
A useful engineering contribution. The framework brings together useful elements of existing spatial reasoning systems into a coherent interface, with reusable scene representations, cached perception features, on-demand object extraction, and composable geometric queries. Although the individual components are established, their integration offers a practical foundation for subsequent research and potential deployment. I particularly appreciate this effort to make the existing paradigm easier to reuse.
-
Broad evaluation with informative failure analysis. Comparisons against the original backbones show substantial improvements on metric and camera-geometry questions. The paper also reports categories where performance declines, giving a useful account of the framework’s capabilities and limitations.
Critical weaknesses
-
The methodological novelty is not huge. The contribution is primarily the organization and implementation of the interface. Controlled comparisons using the same perception outputs would help establish the benefits of this particular design.
-
The evaluation protocol and efficiency evidence need clarification. The paper does not clearly specify evaluation sample counts or whether all benchmarks are evaluated in full. Comparisons with published results may involve different conditions. The reported perception timings also exclude model calls, leaving a gap between evaluation and actual use.
Questions for authors
Were all three benchmarks evaluated in full? If subsets were used, how were they selected, and were the directly rerun baselines evaluated on the same questions?
What are the measured end-to-end latency and average model-call costs of SpaceMCP and SpatialClaw under matched conditions, including preprocessing and its amortization across questions?