eigenlayer-mcp

Most tools have distinct purposes: admin and implementation are getters, changeAdmin, upgradeTo, and upgradeToAndCall are setters, and AdminChanged, BeaconUpgraded, and Upgraded are event subscriptions. However, admin and changeAdmin could be slightly confusing as they both relate to admin functionality, but their descriptions clarify one is a getter and the other a setter.

Naming is inconsistent with mixed conventions: admin and implementation use lowercase, changeAdmin and upgradeTo use camelCase, upgradeToAndCall uses camelCase with 'And', and event names like AdminChanged and BeaconUpgraded use PascalCase. This lack of a uniform pattern makes the set harder to navigate.

With 8 tools, the count is reasonable for managing a smart contract's admin and upgrade functions, covering core operations like getting/setting admin and implementation, and handling events. It's slightly lean but sufficient for the apparent scope.

The tool set covers key aspects of contract management: reading admin and implementation, changing admin, upgrading implementation, and subscribing to relevant events. A minor gap is the lack of tools for broader contract interaction (e.g., pausing or ownership transfer), but the core upgrade lifecycle is well-covered.