No user-submitted related servers found.
Scored across 79 tools
Most domain prefixes (chart_, pine_, replay_, alert_) carve out distinct areas, but several clusters overlap heavily: ui_click vs ui_mouse_click vs ui_hover vs ui_find_element, ui_keyboard vs ui_type_text, and four compile/validate tools (pine_compile, pine_smart_compile, pine_check, pine_analyze) whose boundaries are only explained in prose. chart_scroll_to_date vs chart_set_visible_range and tab_follow_visible vs tab_switch also require reading descriptions to choose correctly.
Nearly every tool is prefixed by its domain (data_, draw_, alert_, replay_, ui_, pane_, tab_, chart_, pine_), making grouping predictable. Ordering within the prefix varies (chart_get_state vs draw_shape vs alert_create vs capture_screenshot), but the convention remains readable and no chaotic mixing of camelCase/snake_case occurs.
79 tools is far beyond a well-scoped set even for a broad desktop-automation domain; many low-level UI primitives (ui_mouse_click, ui_scroll, ui_hover, ui_evaluate) arguably belong behind a single generic action tool. The count forces agents to scan a large, flat surface for routine operations.
Coverage is deep across chart control, Pine scripting, data extraction, replay, alerts, layouts, panes, and watchlists, so core workflows have no dead ends. Minor gaps remain (no watchlist_remove or alert_update, no layout save/delete, no cleanup for panes/scripts), but agents can work around them via ui_evaluate.