No user-submitted related servers found.
Scored across 2 tools
The two tools have completely distinct roles: web_action executes operations, while web_info retrieves state and context. There is no functional overlap, so an agent should never confuse them.
Both tools follow the same 'web_' prefix with a clear noun suffix ('action' vs 'info'). The naming is consistent, short, and predictable, even though it uses nouns rather than verb_noun.
Two tools is on the low end and feels thin for a web automation domain. While every tool is broad and earns its place, the server likely relies on complex schemas to compensate for the minimal count.
The action/info split covers the fundamental read-operate cycle of browser automation, and web_action's ordered actions suggest broad capability. Minor gaps may exist (e.g., no obvious dedicated session-management tool), but the design appears to cover core needs.