No user-submitted related servers found.
Scored across 4 tools
Each tool targets a clearly distinct concern: reading editor state, reading console output, executing a menu action, and refreshing assets. There is no realistic confusion between them, as names and descriptions point to different resources and actions.
All tools share a consistent 'unity_' prefix, but the remainder mixes nouns (status, console) with verb phrases (execute_menu, refresh). It is still highly readable and predictable overall.
Four tools is a focused, reasonable scope for a lightweight editor bridge, though it sits at the thin end and could plausibly include one or two more operations (e.g., play mode control, test running).
The core dev loop is covered: inspect state, read console diagnostics, refresh/import external changes, and run arbitrary menu items as an escape hatch. Direct play mode toggle or test execution would round it out, but the menu escape hatch mitigates most gaps.