Related Servers

Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly divided into 'act' (click, execute, type), 'inspect' (console, dom, events, navigate, network, screenshot, text), and 'session' (connect, create, destroy, escalate, list) categories, each targeting specific browser automation tasks. The descriptions reinforce these distinctions, making misselection unlikely.

Tool names follow a highly consistent verb_noun pattern with a clear prefix structure: 'browser_act_*' for actions, 'browser_inspect_*' for inspection, and 'browser_session_*' for session management. All names use snake_case consistently, and the verb choices (click, execute, type, inspect, connect, create, etc.) are predictable and well-aligned with their functions.

The 15 tools are well-scoped for a browser instrumentation server, covering all essential aspects: session lifecycle management, page inspection, and user interactions. Each tool earns its place without redundancy, and the count is typical for this domain (similar to the GitHub example with 10 tools). No tools feel unnecessary or missing for the core purpose.

The tool surface provides complete coverage for browser automation. It includes session CRUD (create, connect, list, destroy), escalation for actions, comprehensive inspection (dom, text, console, network, events, screenshot, navigation), and core user actions (click, type, execute). There are no obvious gaps; agents can perform full observation and interaction workflows without dead ends.