No user-submitted related servers found.
Scored across 15 tools
Each tool targets a distinct diagnostic phase: protocol listing, frame parsing/validation, live probing, data reading/browsing, capture via proxy/listener, and final diagnosis. Even the two capture retrieval tools (get_proxy_frames vs get_listener_frames) are clearly separated by capture source, and parser/validator/diagnose have non-overlapping purposes.
Most tools follow a clear verb_noun snake_case pattern (list_protocols, validate_frame, probe_device, parse_frame, start_listener, stop_proxy). The only minor deviation is plc_read and plc_browse, which invert the pattern to noun_verb, but the pair is internally consistent and still readable.
15 tools is at the upper edge of the well-scoped range but every tool earns its place in the diagnostic workflow: detection, parsing, validation, capture, reading, browsing, and analysis. There is no redundancy or padding, and the count matches the breadth of the industrial protocol domain.
The tool surface covers the full diagnostic lifecycle: detect/probe devices, parse and validate frames, capture live traffic via proxy or listener, retrieve captured frames, browse address spaces, read PLC data, and produce structured diagnoses. The read-only focus is consistent and intentional, with no dead ends in the workflow.