No user-submitted related servers found.
Scored across 13 tools
Each tool has a distinctly different purpose: page state vs full map, screenshot, navigation (back, scroll), form filling vs single action, waiting, tab lifecycle, and batch map retrieval. There is no meaningful overlap that would cause an agent to select the wrong tool for a given operation.
Tool names consistently use snake_case with action-first verbs (get_, take_, navigate_, scroll_, fill_, wait_, execute_, open_, switch_, list_, close_, batch_get_). The pattern is mostly verb_noun, with minor deviations like 'navigate_back' and 'wait_for' that are still predictable and readable.
13 tools is well within the ideal 3-15 range for a web automation server. Each tool is justified and non-redundant, covering page inspection, interaction, navigation, waiting, screenshot, tab management, and batch processing without excessive granularity.
The tool surface covers the core browsing lifecycle: get page data, interact, fill forms, wait, navigate back, scroll, take screenshots, manage tabs, and batch fetch. Minor gaps include lack of an explicit forward navigation or refresh, and navigation to a URL is implicitly done via get_page_map(url), but these are workable gaps.