No user-submitted related servers found.
Scored across 13 tools
Most tools target clearly distinct phases (session lifecycle, action, evidence capture, replay, repro record, fix verify). However, web_debug_control, web_breakpoint_set, and web_replay_seek all touch pause/step/replay state, and web_issue_capture vs web_replay_seek both deal with retained evidence, creating mild boundary ambiguity.
Every tool follows a strict `web_` prefix plus a noun_verb or noun_action snake_case pattern (web_session_start, web_breakpoint_set, web_fix_verify), with no camelCase or style mixing. The convention is highly predictable across all 13 tools.
13 tools is well within the ideal 3-15 range and each tool maps to a distinct step of a debugging/reproduction workflow. No tool appears redundant or filler.
The surface covers session lifecycle, browser actions, breakpoints, evaluation, evidence capture, replay, reproduction recording, fix verification, and framework-specific inspection. A notable gap is the absence of any breakpoint removal/listing or session cleanup beyond close, but core workflows are otherwise well covered.