No user-submitted related servers found.
Scored across 22 tools
Most tools have clearly distinct purposes: the three planners are separated by space (joint, IK pose, cartesian line), and read-only tools (get_robot_state, get_safety_envelope, get_safety_status, get_motion_status) target different resources despite similar names. The only real risk of confusion is among the stopping/recovery family (stop_motion, estop, reset_estop, error_recovery), but descriptions make the latch/approval semantics explicit enough to guide selection.
Predominantly consistent snake_case verb_noun (get_*, set_*, list_*, plan_*, execute_plan, switch_controllers) with a coherent gripper_* sub-family. A handful of bare noun/verb forms (estop, reset_estop, error_recovery, camera_snapshot, lookup_transform) deviate from the pattern but remain unambiguous.
22 tools is on the heavy side, but the domain genuinely spans planning, execution, monitoring, gripper control, safety policy, recovery, and ROS introspection, so almost every tool earns its place. Nothing looks redundant or like filler.
The surface covers the full lifecycle: introspect envelope/state/ROS graph, plan three ways, execute, monitor, control the gripper and controllers, stop/e-stop/reset, recover, and audit. Minor gaps exist (no explicit plan-inspection or cancel tool beyond stop_motion, no tool-frame/payload configuration), but these are workaroundable and likely intentional policy-side controls.