No user-submitted related servers found.
Scored across 42 tools
Many tools are distinct, but the simple-vs-standard schedule variants (create_simple_schedule vs create_schedule, etc.) are easy to confuse, and run_cleaning_task overlaps with create_task_definition plus start_task. Task, report, resource, and work-mode listing tools also have subtle boundary differences that descriptions only partially clarify.
Most names follow a consistent snake_case verb_noun pattern, such as list_robots, get_robot_status, create_task_definition, and stop_navigation. A few outliers like remember and wait_for_command are slightly less predictable, but the overall convention is stable.
With 42 tools, the surface is heavy for the apparent robot-management domain and exceeds the typical well-scoped range. The duplication of simple and standard schedule CRUD operations makes the set feel bloated rather than tightly scoped.
The server covers robot status, maps, task definitions and execution, reports, schedules, navigation control, command tracking, error lookup, and memory, which is broad lifecycle coverage. Minor gaps remain, such as no arbitrary point-to-point navigation tool, but core robot operations are well represented.