VectorClaw
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VECTOR_HOST | No | Optional IP address of the robot. If omitted, the robot is auto-discovered on the local network. | |
| VECTOR_SERIAL | Yes | The serial number of your Anki Vector robot, printed on the underside of the robot. | |
| VECTOR_AUTO_DRIVE_OFF_CHARGER | No | Set to '1' to automatically drive off the charger before executing drive commands. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vector_setupA | Run the VectorClaw setup wizard: validate Python compatibility, install the Vector SDK if missing, write OpenClaw config, check robot connectivity, and run smoke tests. Returns a structured PASS/FAIL report with actionable remediation steps. Call this tool first when setting up VectorClaw for a new user. |
| vector_sayB | Make the Anki Vector robot speak text aloud. |
| vector_animateB | Play a named animation on the robot. |
| vector_driveB | Move the robot straight and/or turn it in place. |
| vector_drive_off_chargerA | Drive the robot off its charger. |
| vector_drive_on_chargerA | Drive Vector back onto its charger with a configurable timeout. Returns immediately (already_on_charger: true) if Vector is already docked. Requires the charger to be in Vector's recent world model; use vector_scan first if the charger may not have been recently observed. Attempts a motor stop as a best-effort fallback if the maneuver times out. |
| vector_emergency_stopA | Immediately stop all Vector motors. |
| vector_lookB | Capture an image from the robot's front camera. |
| vector_faceB | Display a custom image on the robot's face screen (144×108). |
| vector_poseA | Get the robot's current position and orientation. |
| vector_cubeC | Interact with Vector's cube accessory. |
| vector_statusA | Get robot status (battery level, charging state, etc.). |
| vector_headA | Set Vector's head angle in degrees. Input is clamped to the safe range (-22.0 to 45.0 degrees). |
| vector_liftA | Set Vector's lift/arm height (0.0 = lowest, 1.0 = highest). Input is clamped to the valid range 0.0–1.0. |
| vector_scanA | Make Vector look around in place to scan the environment. |
| vector_find_facesB | Make Vector actively search for faces in the environment. |
| vector_list_visible_facesB | Return the list of faces currently visible to Vector. |
| vector_list_visible_objectsB | Return the list of objects currently visible to Vector. |
| vector_capture_imageA | Capture a single camera frame via camera.capture_single_image. |
| vector_face_detectionA | Return a summary of currently visible faces (no raw image data). |
| vector_vision_resetB | Disable all active vision modes via vision.disable_all_vision_modes. |
| vector_charger_statusB | Return charger and battery state. |
| vector_touch_statusA | Return touch-sensor reading from Vector's back capacitive sensor. |
| vector_proximity_statusA | Return proximity sensor reading from Vector's front IR sensor. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Several tools have effectively the same purpose: vector_look and vector_capture_image both capture a camera frame, vector_status and vector_charger_status both report battery/charging state, and vector_face_detection overlaps heavily with vector_list_visible_faces. An agent could easily select the wrong tool despite the descriptions.
Most tools follow a vector_ + verb_noun pattern (drive, find_faces, capture_image), and the shared prefix makes the set feel unified. A few noun-style names like vector_pose, vector_status, vector_cube, and vector_face deviate slightly, but they are still predictable and readable.
24 tools is at the heavy end for a single server, and redundant pairs inflate the count. However, the robot-control domain legitimately needs many operations for driving, sensors, vision, and display, so the scope is borderline rather than excessive.
The set covers core Vector workflows: movement, docking, camera, speech, animation, face/object detection, head/lift control, sensor status, and setup. Lacking explicit audio capture or a dedicated stop-speaking command are minor gaps that don't create dead ends.