No user-submitted related servers found.
Scored across 16 tools
Most tools are clearly separated by resource and granularity: alarms vs. rules, list vs. get, and channel-level vs. point-level mappings. The only mild risk is between channels_mappings, channels_points_mapping, and channels_unmapped_points, but their descriptions clarify the difference.
The naming generally follows a resource-first snake_case pattern with list/get/stats/status suffixes, which is predictable. Minor inconsistencies exist, such as history_latest not using a verb and alarm rules using alarms_rules vs. business rules using rules.
At 16 tools, the set is slightly over the ideal 3-15 range but still reasonable given the broad domain covering alarms, channels, rules, history, models, routing, and templates. Each tool has a distinct place in the overall surface.
The entire tool surface is read-only: there are no create, update, delete, acknowledge, map, or route configuration operations. This creates significant dead ends, such as listing unmapped points with no way to map them, or viewing alarm rules with no way to modify them.