No user-submitted related servers found.
Scored across 79 tools
Many tools have overlapping purposes, especially the status/snapshot cluster (rba_health_check, rba_unified_status, rba_development_snapshot, rba_context_snapshot, rba_connection_info, rba_ws_status) which all provide similar diagnostic information. Execution tools (rba_send_lua, rba_eval_lua, rba_execute_file, rba_eval_lua_file) also blur boundaries between send, eval, and execute.
Tools use a consistent rba_ prefix and snake_case, but verb usage is inconsistent: some are verb_noun (rba_start_live_session, rba_list_files), while others are noun-only (rba_events, rba_clients) or noun_noun (rba_connection_info, rba_health_check). This mix reduces predictability.
With 79 tools, the set is far too large for most workflows. While the domain is complex, many functions could be consolidated (e.g., multiple snapshot/status tools into one, or combined file operations). This exceeds the typical well-scoped range and adds cognitive overhead.
The tool set provides extensive coverage of the Roblox bridge development lifecycle: connection management, Lua execution, file operations, autoexec configuration, script capsules, watchers, teleportation, screenshots, and debugging. There are no obvious dead ends, and generic eval_lua covers arbitrary Roblox interactions.