No user-submitted related servers found.
Scored across 16 tools
Most tools have clearly distinct purposes, but query_dom, inspect_element, and get_html all read from the DOM and could occasionally be confused. get_page_info and connection_status also share bridge-identity fields, though their primary responsibilities are different.
The get_* and set_* prefixes create a strong, predictable pattern, and click/fill/hover/press_key are intuitive action verbs. connection_status breaks the get_ convention and query_dom/inspect_element are less pattern-aligned, but overall naming remains readable and consistent.
At 16 tools, this is slightly above the ideal 3-15 range, but the breadth is justified by the server's browser-debugging scope. The count feels reasonable rather than bloated.
The toolset covers the core debugging lifecycle: reading DOM/console/network state, interacting with the page, previewing changes, and resetting overrides. Obvious gaps like explicit navigation, waiting for conditions, or screenshots are missing but are not fatal to the main workflows.