ROS MCP exhibits uneven quality across 15 tools. Strengths: all tools have names starting with action verbs (get_, set_, delete_), and tool annotations (readOnlyHint/destructiveHint) are declared in the feature list. Critical weaknesses: (1) Descriptions vary wildly in quality, some are long and example-heavy (get_actions, get_action_details), others are minimal or reference external files; (2) Most tools show schema definitions (parameters declared with types and descriptions), but several parameter descriptions are single sentences without context or constraints; (3) No documented output schemas, the rubric requires 'Document the output schema. LLMs need to know what fields to expect.' Without it, agents cannot reliably chain tools; (4) Error handling is not visible in the provided code snippets, no recovery guidance, retryability hints, or actionable error messages; (5) Two tools (connect_to_robot, ping_robot) expose network timeouts as parameters, which is unusual and may leak implementation details to the LLM; (6) get_connected_robots lacks clarity on whether it requires a prior connection or auto-discovers; (7) analyze_previously_received_image references 'saved by any ROS operation' but the mechanism for this saving is not explained in the tool description.
Analyze a previously received image that was saved by any ROS operation. Images can be received from: - Any topic containing image data (not just topics with 'Image' in the name) - Service responses containing image data - subscribe_once() or subscribe_for_duration() operations Use this tool to analyze the saved image after receiving it from any source.
Connect to the robot by setting the IP/port. This tool also tests connectivity to confirm that the robot is reachable and the port is open. Example: connect_to_robot(ip='192.168.1.100', port=9090)
Delete a ROS parameter. Works only with ROS 2. Example: delete_parameter('/turtlesim:background_b')
Get complete action details including type, goal, result, and feedback structures. Works only with ROS 2. Example: get_action_details('/turtle1/rotate_absolute')
Get action status for a specific action name. Works only with ROS 2. Example: get_action_status('/fibonacci')
No documented output schemas for any tool. LLMs cannot know what fields to expect from responses, preventing reliable tool chaining and forcing agents to guess at downstream parameter mappings.
Descriptions for discovery tools (get_nodes, get_actions, get_connected_robots) lack context about WHEN to call them in a workflow and WHAT structure they reveal. e.g., 'Get list of all currently running ROS nodes. Example: get_nodes()' is 72 chars, too terse to guide LLM selection.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | C | 61 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 49 | - | v1 |
Get list of all available ROS actions. Works only with ROS 2. Example: get_actions()
Detect connected robots by finding active cmd_vel topics on the ROS network. Works with any robot — no hardcoded names. Returns the cmd_vel topic and message type for each robot, ready to pass directly to move_by_distance / turn_by_angle / move_robots. Call this when you need to discover robot topics before issuing motion commands. Example: get_connected_robots()
Get detailed information about a specific node including its publishers, subscribers, and services. Example: get_node_details('/turtlesim')
Get list of all currently running ROS nodes. Example: get_nodes()
Get a single ROS parameter value by name. Works only with ROS 2. Example: get_parameter('/turtlesim:background_b')
Get comprehensive details about a specific ROS parameter including value, type, and metadata. Works only with ROS 2. Example: get_parameter_details('/turtlesim:background_r')
Get list of all ROS parameter names for a specific node. Works only with ROS 2. Example: get_parameters('cam2image') get_parameters('/cam2image')
Check if a ROS parameter exists. Works only with ROS 2. Example: has_parameter('/turtlesim:background_b')
Ping a robot's IP address and check if a specific port is open. A successful ping to the IP but not the port can indicate that ROSbridge is not running. Example: ping_robot(ip='192.168.1.100', port=9090)
Set a single ROS parameter value. Works only with ROS 2. Example: set_parameter('/turtlesim:background_b', '255')
Parameter descriptions lack constraints and context. 'ping_timeout' and 'port_timeout' are exposed as parameters but have no documented ranges, units (seconds assumed), or whether they can be overridden at the server level. LLMs may pass invalid values.
No error handling guidance visible in tool definitions. No indication of whether failures are retryable (e.g., network timeout on ping_robot) or permanent (e.g., invalid parameter name). Descriptions do not include recovery paths such as 'If parameter not found, call get_parameters() to discover available names.'
analyze_previously_received_image description references a mechanism ('Images can be received from…') but does not explain HOW images are saved or WHEN they become available. The phrase 'saved by any ROS operation' is vague, does the server auto-save? Must the user invoke a separate save call?
Three tools (get_actions, get_action_details, get_action_status) have descriptions stating 'Works only with ROS 2' but lack guidance on what happens if called on ROS 1 systems. Should the error message guide the user, or should the tool pre-check the ROS version?
get_connected_robots description is verbose (350+ chars) and includes implementation details ('finds active cmd_vel topics'). Simplify to 150 - 200 chars focusing on WHAT it returns and WHEN to call it, not HOW it works internally.