Bilkent University · 2026

ToolMind:
VLM-Guided Spatial Reasoning for Robotic Tool Use

Süleyman Talha Belen Yunus Emre Kök Yusuf Buğra Yazıcıoğlu Mehmet Emin Yakşi

Department of Electrical and Electronics Engineering, Bilkent University

Full ToolMind overview demo across all three constrained manipulation scenarios: wall retrieval, screwdriver insertion, and shelf retrieval.

We couple VLM semantic reasoning (GPT-5.5) with depth-based geometric refinement to drive multi-phase robotic tool use. ToolMind uses Structured Chain-of-Thought prompting to mitigate spatial myopia, while DBSCAN cluster labels and depth back-projection turn VLM outputs into actionable 3D keypoints.

Abstract

ToolMind is a dual-modality pipeline for scenario-specific sequential robotic tool use. Given RGB-D observations of a tabletop scene, the system identifies the correct tool, predicts task-relevant grasp, functional contact, and waypoint keypoints, and executes a multi-phase manipulation sequence. GPT-5.5 handles semantic scene understanding, tool selection, structured keypoint reasoning, and waypoint generation, while a depth-based geometric module refines coarse VLM outputs into precise 3D keypoints.

The central challenge is spatial myopia: VLMs often regress keypoints toward object centroids instead of the task-relevant extremities needed for tool use. We mitigate this with a Structured Chain-of-Thought JSON prompting strategy that forces geometry → grasp anchor → contact tip reasoning before coordinate regression. The resulting keypoints drive KOMO-based trajectory optimization in a simulated Franka Emika Panda environment across wall retrieval, screwdriver insertion, and shelf retrieval tasks.

The pipeline requires no task-specific VLM retraining and operates in an open-world style: DBSCAN-derived cluster labels and per-cluster geometry summaries anchor the model's attention, while depth back-projection, point-cloud snapping, PCA geometry, and antipodal search convert VLM predictions into physically feasible robot actions.

Key Contributions

Cluster-anchored VLM reasoning

DBSCAN clusters are projected back to RGB views as labelled regions, turning open image regression into a structured selection-and-localization problem.

Structured CoT against spatial myopia

The prompt requires explicit geometry, grasp-anchor, and contact-tip reasoning before GPT-5.5 is allowed to output coordinates.

Depth-based 3D refinement

VLM pixels are lifted through the registered depth channel, snapped to the selected tool point cloud, and refined with PCA and antipodal search.

Scenario-specific KOMO execution

The refined keypoints guide grasping, positioning, and execution phases for pull, insert/rotate, and sweep/push manipulation.

Method

Four tightly-coupled stages connect raw RGB-D perception to physics-based trajectory execution. GPT-5.5 acts as the semantic backbone — selecting tools, predicting keypoints, and generating motion planning waypoints.

Stage 01
📷
Scene Perception

RGB-D capture from top-down + oblique views. Depth back-projected to 3D. DBSCAN clustering, alphabetic object labeling.

Stage 02
🧠
VLM Reasoning

GPT-5.5 receives annotated RGB + cluster summaries. Outputs tool label, grasp region, contact pixel, and motion planning waypoints via CoT prompting.

Stage 03
📐
Geometric Refinement

Contact pixel back-projected to 3D via depth channel. PCA axis estimation, antipodal grasp search, vector-based tool orientation.

Stage 04
🤖
KOMO Execution

Multi-phase trajectory optimization: grasp → position → execute. Collision avoidance + joint-limit constraints on Franka Panda.

Illustrative Intermediate Outputs

The original stage summary stays above. Below, you can directly show four example figures: DBSCAN + point cloud, clusters, VLM output for grasp, and VLM waypoint generation.

Stage 01 DBSCAN + point cloud
DBSCAN + point cloud
+
DBSCAN + point cloud DBSCAN scene point cloud

Back-projected scene point cloud before semantic reasoning.

Stage 02 Clusters
Clustered scene output
+
Cluster labeling Projected cluster labels

DBSCAN clusters and alphabetic object labels prepared for the VLM.

Stage 03 VLM output for grasp
VLM grasp output
+
VLM output for grasp VLM grasp/contact output

Annotated VLM prediction for tool selection, grasp region, and functional contact pixel.

Stage 04 VLM waypoint generation
VLM waypoint output
+
VLM waypoint generation VLM waypoint output

VLM-generated semantic waypoints that later guide the KOMO trajectory optimization.

Depth Channel: 2D Pixel → 3D World

The VLM operates on RGB images and outputs pixel coordinates [u, v]. These are lifted to 3D world-frame keypoints using the depth channel via camera intrinsics.

The resulting camera-frame point is transformed to world coordinates using the camera extrinsics. The VLM-predicted functional contact pixel is back-projected this way and then snapped to the nearest point on the selected tool's point cloud, yielding the refined 3D contact keypoint c.

VLM's Role in Motion Planning

Beyond tool selection and keypoint prediction, GPT-5.5 serves as a semantic motion planning assistant — providing waypoints that guide the KOMO trajectory optimizer for each scenario.

🗺️ Waypoint Generation

The VLM is queried for approach angles, target positions, and directional vectors. These serve as semantic waypoints that constrain the KOMO optimizer's trajectory phases.

🔄 Multi-Query Tip Localization

The VLM is queried multiple times to identify the functional tool tip or contact point from annotated views and cluster context. This is especially useful for selecting the distal end opposite the grasp region instead of treating the grasp side as the contact tip.

📍 Orientation Estimation

For constrained spaces, the VLM identifies key geometric points (A, B for sweep direction; G, C for tool axis) that drive vector-based tool orientation alignment.

🧩 Semantic Scene Understanding

VLM analyzes cluster positions, object identities, and spatial relationships to reason about which side to approach from and how far objects must be moved to become reachable.

Structured Chain-of-Thought Prompting

To counter spatial myopia, the JSON schema mandates three explicit reasoning steps before any coordinate regression is allowed:

1
step1_geometry_analysis

Describe the physical shape of the selected tool and locate its extreme boundaries in the image.

2
step2_grasp_location

Identify the exact region designated for robotic contact — e.g., "the right-most end of the stick".

3
step3_contact_tip_location

Using the grasp location as anchor, deduce the exact opposite functional extremity. Only then is the pixel coordinate [u, v] requested.

Example: Shelf scenario reasoning for C-point localization

This figure illustrates how the Chain-of-Thought prompt guides the model to find the functional contact point C in the shelf scenario by first identifying tool extremities, then anchoring the grasp, and finally selecting the distal pushing tip.

Chain-of-Thought example for shelf scenario C-point reasoning
Upload the example figure as CoT.png
to show the shelf scenario C-point reasoning image here.

Illustrative example of the reasoning process used to avoid spatial myopia when predicting the functional contact point for the shelf task.

Prompt Levels (P0 – P3)

P0 — Minimal

Single instruction: select a tool and output pixel coordinates. No schema, no task context.

P1 — Structured

Defined JSON schema with named fields for tool, grasp region, pixel coordinates, and confidence. No scenario context.

P2 — Scenario-Aware

P1 plus full scene context and, where applicable, calibrated handle coordinate hints from gt.json.

P3 — Anti-Failure BEST

P2 plus explicit anti-failure constraints such as "do not grasp the functional tip" and self-check reasoning fields.

Evaluation Scenarios

Three constrained tabletop manipulation tasks. Each scenario details the specific role GPT-5.5 plays in guiding motion planning beyond mere tool selection.

Scenario 1 Wall Retrieval
+
Scenario 1 image Upload as scenario1_wall_retrieval.png
or replace the image path.

Scenario 1 · Wall Retrieval

Target object behind a rigid wall, retrieved by grasping one end of a rigid tool and dragging.

PULL
Scenario 2 Screwdriver Insertion
+
Scenario 2 image Upload as scenario2_screwdriver_insertion.png
or replace the image path.

Scenario 2 · Screwdriver Insertion

Rotational actuation of a target using a screwdriver-like tool with a VLM-determined rotation waypoint.

INSERT / ROTATE
Scenario 3 Shelf Retrieval
+
Scenario 3 image Upload as scenario3_shelf_retrieval.png
or replace the image path.

Scenario 3 · Shelf Retrieval

Cup under a low-clearance shelf swept out with vector-aligned tool orientation and brought into the robot's reachable workspace.

SWEEP → GRASP

VLM Contributions per Scenario

🧱

Scenario 1: Wall Retrieval (Pulling)

PULL · Tip Localization

A target object is placed behind a rigid wall, beyond the robot's direct reach. The system selects a long, rigid tool, grasps it from one end, and uses the opposite tip to drag the object into the reachable workspace. The primary geometric challenge is accurate functional tip localization: the contact point must be at the far end of the tool, not its center.

VLM's role in motion planning

During the motion planning stage, the VLM semantically understands the environment and performs semantic planning over the detected clusters. It is queried to determine the approach angle and the direction in which the functional tip should be oriented — acting as a waypoint generator. The functional tip is then aligned toward this VLM-defined point. Afterwards, the VLM is queried a second time to determine how far the target must be dragged so that it becomes reachable by the robot, providing a drag endpoint waypoint that terminates the pull motion.

🔩

Scenario 2: Screwdriver Insertion

INSERT / ROTATE · Non-translational Planning

A target object requires actuation via a rotational motion. The VLM selects a screwdriver-like tool from the segmented point cloud clusters, and the best antipodal grasp point is computed within the VLM-specified handle region.

VLM's role in motion planning

The VLM analyzes the scene and determines an appropriate rotation waypoint for the screwing motion. This waypoint is also used to align the tool along the vertical axis before the screw motion begins. Once the functional tip (back-projected to 3D from the VLM's contact pixel via the depth channel) reaches the target position, the KOMO planner executes the rotational trajectory. The VLM thus guides a non-translational end-effector motion entirely through semantic scene reasoning.

📦

Scenario 3: Shelf Retrieval (Sweeping)

SWEEP → GRASP · Constrained Insertion

A cup placed under a low-clearance shelf cannot initially be reached by the robot. The robot must navigate a pushing tool through the narrow gap and sweep the cup into a position within the robot's reachable workspace. This is the most geometrically constrained scenario: incorrect tool orientation causes shelf collisions or joint-limit violations.

VLM's role in motion planning

The VLM is queried in a Chain-of-Thought manner to identify the functional tip (C) and grasp point (G), constructing the tool axis vector GC. It also determines two points A and B behind the shelf edges — one near the robot side, one at the far side — defining the sweep direction vector AB. The tool orientation is then adjusted until AB ⊥ GC (computed via dot product), preventing shelf collisions. The robot sweeps with the tool guided by the VLM-defined point A and height. After sweeping, the cup is brought into a position within the robot's reachable workspace. This multi-query VLM strategy makes the pipeline robust to domain randomization and varying initial tool placements.

Scenario Rollouts (Simulation)

Wall Retrieval

Screwdriver Insertion

Shelf Retrieval

Results

Each scenario ablation is run as 3 scene variants × 4 prompts × 5 repeats = 60 VLM calls. We evaluate prompt detail, visual cluster grounding, and model size. Annotated mode uses DBSCAN-derived labels and bounding boxes, while raw mode removes these anchors. Metrics follow the final report: Tool = correct tool selection, Hit = 2D grasp hit rate, AFR = antipodal feasibility rate, and Dev. = grasp deviation.

Table I · Wall Retrieval Ablation

Wall retrieval strongly benefits from explicit anti-failure guidance. P3 gives the highest hit rate and the lowest deviation in every reported setting.

ModelModePromptToolHitAFRDev.
4oAnn.P00.570.000.07210.2 mm
4oAnn.P10.670.000.08231.5 mm
4oAnn.P20.730.130.20160.6 mm
4oAnn.P3 ★0.930.870.8732.8 mm
4oRawP00.730.000.00220.4 mm
4oRawP10.720.290.29220.3 mm
4oRawP20.870.000.00245.7 mm
4oRawP3 ★1.001.000.9317.6 mm
4o-miniAnn.P00.900.200.07119.1 mm
4o-miniAnn.P10.700.200.00131.9 mm
4o-miniAnn.P20.770.070.07185.2 mm
4o-miniAnn.P3 ★0.950.730.337.1 mm

Table II · Screwdriver Insertion Ablation

Screwdriver insertion improves progressively from P0 to P3. Minimal prompts can produce very large deviations, while P2/P3 substantially stabilize spatial localization.

ModelModePromptToolHitAFRDev.
4oAnn.P00.700.100.2047969.0 mm
4oAnn.P10.670.100.6571.2 mm
4oAnn.P20.800.670.651.1 mm
4oAnn.P3 ★0.800.830.650.2 mm
4oRawP00.520.030.1327037.0 mm
4oRawP10.500.150.20215.7 mm
4oRawP20.700.460.3737.4 mm
4oRawP3 ★0.710.600.494.5 mm
4o-miniRawP00.060.040.203252.4 mm
4o-miniRawP10.560.300.3748.7 mm
4o-miniRawP20.820.540.6816.1 mm
4o-miniRawP3 ★0.740.720.698.0 mm
4o-miniAnn.P00.720.170.431652.0 mm
4o-miniAnn.P10.690.320.4938.3 mm
4o-miniAnn.P20.740.670.568.5 mm
4o-miniAnn.P3 ★0.810.830.770.7 mm

Table III · Shelf Retrieval Ablation

Shelf retrieval is the hardest setting because the model must identify both the correct tool region and the functional end for sweeping. P3 improves tool selection and reduces deviation across all reported shelf settings.

ModelModePromptToolHitAFRDev.
4oAnn.P00.420.250.07136.7 mm
4oAnn.P10.650.300.05147.7 mm
4oAnn.P20.700.050.07186.5 mm
4oAnn.P3 ★0.900.650.0756.1 mm
4oRawP00.620.150.04112.1 mm
4oRawP10.700.200.02132.1 mm
4oRawP20.700.050.07186.5 mm
4oRawP3 ★0.900.550.0656.1 mm
4o-miniAnn.P00.780.200.05125.1 mm
4o-miniAnn.P10.760.300.00149.1 mm
4o-miniAnn.P20.790.070.07191.5 mm
4o-miniAnn.P3 ★0.900.550.2728.1 mm

End-to-End CoT Rollout Ablation

Structured CoT has the strongest impact in the shelf scenario, where success improves from 3/10 to 6/10. The improvement comes mainly from fewer functional contact-point failures.

ScenarioWith CoTWithout CoT
Wall retrieval8 / 107 / 10
Screwdriver insertion7 / 107 / 10
Shelf retrieval6 / 103 / 10

Shelf Rollout Analysis

With Structured CoT

In the shelf scenario, 6 out of 10 rollouts are successful. Among the 4 failures, 2 are caused by selecting the wrong A–B shelf-edge pair, while the other 2 occur because the predicted C point is placed on the same tool end as the grasp instead of the opposite functional tip.

Before CoT

Before adding Chain-of-Thought reasoning, only 3 out of 10 shelf rollouts were successful. The main failure mode was spatial myopia: C was often predicted near the grasp region instead of the distal contact tip. In those failures, 2 came from the wrong A–B edge pair and 5 came from incorrect C-point selection.

Table IV: Shelf Failure Breakdown (10 rollouts)
With CoT Without CoT
Successful rollouts 6 / 10 3 / 10
Failure breakdown
Wrong A–B edge pair 2 2
C placed at same end as grasp 2 5
Total failures 4 7

Additional Result Videos

Screwdriver Wrong Waypoint

Failure case where the VLM predicts an incorrect waypoint for screwdriver insertion, causing the tool tip to approach the target with the wrong spatial alignment.

Wall Wrong Tool Selection

Failure case where the VLM selects an unsuitable tool for the wall-retrieval task, preventing the robot from correctly pulling the target object into the reachable workspace.

Key Findings

Structured CoT targets functional contact localization

The main shelf gain comes from reducing C-placement failures from 5 to 2; the A–B edge-pair error stays at 2 failures in both settings.

Cluster labels reduce ungrounded coordinate regression

DBSCAN-derived labels and cluster summaries anchor the VLM to candidate tool regions, converting raw coordinate regression into selection-then-localization.

Shelf retrieval is the hardest scenario

The shelf task requires relational geometry over A, B, grasp G, and functional contact C, making it more sensitive to spatial myopia than wall or screwdriver tasks.

Execution remains mostly open-loop

Once the KOMO trajectory is generated, the system does not yet re-plan after unexpected slip or contact; closed-loop recovery is a natural next step.