ros2-doctor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ROS_DOMAIN_ID | No | ROS domain ID the server should see robots on. Set it to match yours, or pass `domain_id` in a tool call instead. | 0 |
| ROS2_DOCTOR_ARM_CMD | No | Override the command used to run the arm doctor; the doctors are found on PATH (armdoc), else through `ros2 run`. Example: "ros2 run armdoc armdoc". | |
| ROS2_DOCTOR_NAV2_CMD | No | Override the command used to run the nav2_doctor; the doctors are found on PATH (nav2_doctor), else through `ros2 run`. Example: "python3 -m nav2_doctor.doctor". |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| diagnose_robotA | Start here. Looks at the ROS graph, detects which stacks are present (Nav2, a ros2_control or MoveIt arm, SLAM, cameras), runs every doctor that applies in parallel and returns one merged verdict, errors first, each finding tagged with its source. Good for mobile manipulators. Read-only. |
| diagnose_nav2A | Watch a running Nav2 stack and name why the robot is not moving (stale TF, dead odom/scan, inactive lifecycle nodes, no cmd_vel, flapping goals ...). Read-only. Returns ok and findings with hints. |
| nav2_readyB | Pre-flight check for Nav2: ok is true only if every server is active and the streams are alive. |
| diagnose_armA | Watch a ros2_control / MoveIt 2 arm and name why it is not moving (inactive controller, silent joint_states, joint at a limit, stalled trajectory, missing move_group ...). Read-only. |
| arm_readyB | Pre-flight check for a ros2_control arm: ok only if it can move now. |
| diagnose_slamB | Watch a running SLAM (slam_toolbox, Cartographer, RTAB-Map, ORB-SLAM3) and report map stalls, lost tracking, odometry drift and missing loop closures. Read-only. Uses slam_doctor. |
| diagnose_perceptionA | Watch the cameras, depth sensors and point clouds on a running robot and report a dead or stale stream, low rate, dark, blown-out or frozen images, mostly invalid depth, empty clouds and missing camera_info. Read-only. Uses percept_doctor. |
| analyze_forceA | Offline verdict on a recorded contact-force run (peg-in-hole, press, push; CSV): jammed or not, inserted or not, peak and steady force, time in contact. Needs no robot. cols maps CSV columns, e.g. t=time,f_axial=Fz. |
| check_reachA | Can a UR arm (ur3 or ur5e) reach a tool-down pose at x, y, z metres in the base frame? Returns reachable, the IK error, manipulability and joint-limit margin. Offline, no robot needed (MuJoCo IK via reachlens). |
| score_mapA | Score a saved occupancy map (map_saver .yaml) against a ground-truth map: coverage, wall recall and precision, false-free area. align=true searches for the best translation first. Offline (nav_explore_eval). |
| ros_graphA | List the nodes and topics visible on a ROS domain (read-only). Use it first when a doctor reports that nothing is visible, to find the right domain or namespace. |
| analyze_trajectoryA | Offline quality check of a recorded joint trajectory (CSV, JSON or rosbag2) with trajlens: jerk spikes, limit violations, slow profiles, gaps. Needs no running robot. urdf adds joint limits. |
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 12 tools
The core families are clear: diagnose_* tools for deep read-only verdicts, *_ready for boolean pre-flight checks, analyze_*/check_*/score_map for offline post-hoc analysis, and ros_graph for graph introspection. The main soft spot is that diagnose_robot (aggregates all stacks) overlaps with the per-stack diagnose_nav2 / diagnose_arm / diagnose_slam / diagnose_perception, which could cause an agent to hesitate, though "Start here" and "merged verdict" mitigate this. diagnose_nav2 vs nav2_ready and diagnose_arm vs arm_ready are close in topic but differ clearly in output shape (findings vs boolean).
All names use consistent snake_case and mostly follow verb_object (diagnose_*, analyze_*, check_reach, score_map), with a small coherent second family noun_ready (nav2_ready, arm_ready) and one noun_noun outlier (ros_graph). The _ready suffix family is internally predictable, so the deviation reads as intentional rather than sloppy. Minor inconsistency between verb-led and noun-led names keeps it from a 5.
Twelve tools is squarely in the well-scoped range and each has a distinct job: five online stack diagnostics, two readiness checks, one graph lister, and four offline analyzers. Nothing appears redundant enough to cut, and no obvious category is missing a tool that would need to be bolted on later. The split between online and offline concerns is a sensible scoping of the server's purpose.
Coverage across the ROS2 debugging lifecycle is strong: graph/domain discovery (ros_graph), per-stack diagnostics (Nav2, arm, SLAM, perception), pre-flight readiness, and offline evaluation of force, reach, maps and trajectories. Gaps are minor but real: ready checks exist only for Nav2 and the arm (not SLAM/perception), and there is no dedicated TF-tree or log/dmesg inspection tool despite stale TF being a cited failure mode. These are workable around via the diagnose_* hints rather than hard dead ends.