No user-submitted related servers found.
Scored across 122 tools
Multiple overlapping tool families create real confusion: three separate task/run systems (oc_task_*, oc_task_run_*, oc_run_*) have nearly identical start/get/list/cancel verbs, and several page-reading tools (read_page, inspect, page_content, extract_data, oc_observe) have fuzzy boundaries. Element location is split across find, query_dom, vision_find, oc_query, and oc_observe, while interact/act/computer require careful reading to distinguish. Detailed descriptions help, but the sheer number of near-duplicate surfaces will cause misselection.
The oc_ prefixed tools follow a reasonably consistent verb_noun pattern (oc_task_run_start, oc_session_snapshot), but the legacy non-prefixed tools mix conventions wildly: some are verb_noun (read_page, fill_form), others noun_verb (page_screenshot, page_reload), and several are bare nouns (computer, network, storage, cookies, memory). The confusingly similar oc_task_run_* vs oc_task_* prefixes and odd names like javascript_tool and batch_paginate further erode consistency.
122 tools is far beyond any reasonable scope for a browser automation server. There are multiple redundant subsystems (three task/run ledgers, at least five page-reading tools, three performance analyzers, two network capture tools) that inflate the surface without adding proportionate capability. This is a textbook case of tool sprawl that will overwhelm agents and add selection latency.
The browser automation domain is very thoroughly covered — navigation, reading, interaction, forms, network, performance, crawling, screenshots, and workflows all have extensive support with no obvious dead ends or missing core operations. If anything, completeness is over-achieved at the cost of coherence; the sprawl means completeness is high but at the expense of the other dimensions.