No user-submitted related servers found.
Scored across 24 tools
Several tools have overlapping purposes: antigravity_verify_and_screenshot vs call_antigravity_verifier, antigravity_gui_task_status vs codex_gravity_completion_status, and codex_gui_ask vs call_codex_architect are easy to confuse. Descriptions are detailed but the boundaries between direct GUI control, verifier calls, and completion watches remain unclear.
The set mixes multiple conventions: antigravity_*, call_*, codex_gui_*, codex_gravity_*, and team_*, with verbs appearing sometimes first, sometimes last. Names like antigravity_verify_and_screenshot and codex_gravity_watch_completion are readable but do not follow a predictable verb_noun pattern.
At 24 tools this is heavy for an orchestration bridge, and several status/cancel/watch tools feel like separate surface areas rather than distinct capabilities. The count is borderline but not extreme for a two-agent coordination system.
Core workflows are covered: task start, status, follow-up, completion watches, team sessions, transcripts, reports, and decision logs. However, there is no explicit cancel/stop for an Antigravity GUI task and no obvious session-listing operation, leaving notable gaps in lifecycle coverage.