No user-submitted related servers found.
Scored across 51 tools
Most tools map cleanly to a distinct resource and action, and the singular/plural pairs (e.g. get_time_spec vs get_time_specs) are clearly explained. A few sets such as ping_app vs check_connection, get_portal_states vs get_portal_statuses, and the access-history tools could cause misselection when skimming, but the detailed descriptions disambiguate them.
The dominant get_<entity> / get_<entity>s pattern is predictable and applied across most of the 51 tools. It is diluted by a few different verb styles (check_connection, ping_app, search_person_data, find_portals, list_events, get_guide), but there is no chaotic casing or inconsistent pluralization.
At 51 tools, the surface is far beyond the well-scoped range and even exceeds the 25+ 'too many' threshold. While each tool maps to an NBAPI read command, the sheer number makes the set unwieldy and in need of consolidation or modularization.
The read surface covers many NetBox entities, but there are zero create/update/delete tools, so agents can query but not manage the system. The gap is especially visible because get_locations references set_threat_level and the guide mentions write-safety, yet no such tool is exposed.