No user-submitted related servers found.
Scored across 51 tools
Multiple tools have unclear boundaries, especially between get_network_status, get_network_health, and get_deep_dive, as well as between get_bandwidth_stats, get_dpi_stats, and get_client_dpi. The ensure_ vs update_ rule pairs also overlap in purpose, making it easy for an agent to pick the wrong tool.
Most tools follow a readable verb_noun pattern, but read operations inconsistently mix get_, list_, and search_. The ensure_ and update_ rule tools are also semantically redundant in naming, though the overall style is still understandable.
With 51 tools, this server is extremely large and unwieldy for an agent to navigate. Many health, DPI, client, and rule-management operations could be consolidated, and the sheer count creates significant selection overhead.
Read coverage is broad: status, topology, devices, clients, configs, firewall rules, port forwards, traffic rules, groups, and tags are all present. However, several lifecycle gaps exist, including no create/update/delete for Wi-Fi or network configs, no update/delete for firewall rules or user groups, no firmware upgrade action, and no voucher management beyond creation.