No user-submitted related servers found.
Scored across 27 tools
Most tools have a clear niche, and descriptions explicitly resolve the main overlaps (browser_invoke vs browser_fill/browser_click, browser_read vs browser_ask vs browser_look vs browser_screenshot). However there is genuine redundancy in the action/read space—clicking can be done via browser_click, browser_act, or browser_invoke—so selection still requires care. The guidance text largely saves it, keeping it at mostly distinct.
The 23 browser tools all follow a clean browser_<verb> pattern (browser_click, browser_fill, browser_navigate), which is highly predictable. The four task-level tools (task_status, delegate_goal, answer_task) break the pattern with mixed noun_verb/verb_noun ordering, a minor deviation rather than chaos.
27 tools is heavy and pushes past the comfortable range, with arguably too many overlapping read/act primitives (read, ask, look, inspect, extract, capabilities). Each does cover a distinct browser capability, so it is defensible rather than padded, but the set is borderline oversized for the domain.
The surface covers the full browser-driving lifecycle: navigation and tabs, form discovery and submission, raw actions, waits, scrolling, uploads/downloads, dialogs, screenshots, console, network, and JS eval. The delegation flow (delegate_goal, task_status, answer_task) closes the human-in-the-loop gap, leaving no obvious dead ends.