No user-submitted related servers found.
Scored across 51 tools
Tools are mostly distinct by resource and action, and singular/plural pairs follow a predictable pattern. Portal-related tools (get_portals, find_portals, get_portal_statuses, get_portal_groups) and history tools could momentarily overlap, but the detailed descriptions resolve boundaries clearly.
Naming is predominantly a consistent snake_case get_* pattern, with minor deviations like list_events, search_person_data, find_portals, check_connection, and ping_app. These deviations are readable and clearly signal the tool's special behavior.
At 51 tools, the surface far exceeds the typical 3-15 well-scoped range and crosses the rubric's 50+ extreme-mismatch threshold. Even though each tool maps to a distinct API endpoint, the sheer count imposes a heavy selection burden on agents.
The toolset is entirely read-only, with no create, update, or delete operations for the access-control domain. Read coverage is broad, but the absence of lifecycle write operations (e.g., setting unlock windows, granting access) is a significant gap that will block management tasks.