No user-submitted related servers found.
Scored across 18 tools
Tools are mostly distinct: get_device vs list_devices, get_interface vs list_interfaces, and get_wifi_status vs list_interfaces are clarified by descriptions. The raw rci_call could be used instead of specific tools but is explicitly positioned as a fallback, so misselection risk is low. Minor overlap between get_wifi_status and list_interfaces remains.
All tool names are snake_case, and nearly all follow a verb_noun pattern (get_, list_, update_, set_, create_, delete_, backup_, save_). The outlier rci_call breaks the pattern slightly, but otherwise naming is highly predictable.
18 tools is slightly above the ideal 3–15 range, but each tool targets a distinct router management operation (devices, interfaces, segments, config, diagnostics). The breadth reflects the complex domain, so the count is reasonable, though not minimal.
Core lifecycle for devices (list/get/update) and segments (list/create/delete) is present, and config save/backup are covered. However, notable gaps exist: no dedicated tools for modifying Wi-Fi settings, static routes, policies (only list), interface creation, or firmware/reboot; rci_call provides a workaround but the surface feels incomplete for common router tasks.