Open-source AI agent framework for robotics — 49 MCP tools for Claude, Cursor, or any AI to control ROS 1/2 robots, with YOLO+CLIP vision, MuJoCo sim, and fleet management
RoboRun exposes 11 robotics tools with basic schemas and descriptions. Most tools have descriptions (10/11), but quality is inconsistent: some are action-oriented ('Send a direct velocity command'), others vague ('Get current robot telemetry'). Parameter descriptions are sparse, many lack units, ranges, or constraints. Schemas are present but minimal: most parameters lack type info or validation rules. No output schemas documented. Error handling is absent from descriptions. Tool naming is generally clear (move, takeoff, land, goto_waypoint) but some are generic (get_telemetry, get_trajectory). No tool annotations (readOnlyHint, destructiveHint) despite clear WRITE/READ/DESTRUCTIVE risk labels in metadata. Composition is reasonable, tools are single-purpose, but chaining support is unclear (e.g., does find_object return coordinates for goto_waypoint?).
Actively search for an object by rotating the robot and checking the camera at each step. Returns when found or after full rotation.
Delete a fact from persistent memory by ID.
Get current robot telemetry — battery, position, orientation, velocity, joint states.
Get the recorded trajectory as timestamped poses.
Fly to a 3D waypoint (drone only).
Land the drone at current position.
Search the robot's spatial memory for past observations using CLIP semantic search.
No output schemas documented for any tool. LLMs cannot plan downstream calls or extract required fields (e.g., does find_object return x,y,z coordinates for goto_waypoint?).
Parameter descriptions lack units, ranges, and constraints. E.g., move.linear_x says 'm/s, e.g. 0.3' but no min/max bounds; memory_search.top_k has no default or range; goto_waypoint coordinates have no coordinate system or bounds.
Tool descriptions are too generic and lack context for LLM selection. 'Get current robot telemetry' does not explain WHEN to call it vs other discovery tools, or what fields are returned. 'Land the drone at current position' omits prerequisites (must be armed/flying).
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Send a direct velocity command to the robot (/cmd_vel). Fast — no MCP round-trip. linear_x: forward (+) / back (-). angular_z: left (+) / right (-).
Search persistent memory for relevant facts by keyword.
Store a fact in persistent memory. Facts persist across sessions and are shared between agents.
Arm and take off to specified altitude (drone only).
No error handling guidance in tool descriptions. Destructive tools (forget, land, takeoff) lack confirmation or dry-run patterns. No recovery hints (e.g., 'If object not found, try memory_search').
Tool annotations missing. Risk metadata (WRITE, READ_ONLY, DESTRUCTIVE) exists in server metadata but not exposed as MCP tool annotations (readOnlyHint, destructiveHint, idempotentHint), preventing clients from applying safety policies.