lido-mcp

Each tool has a clearly distinct purpose with no overlap: appId, implementation, isDepositable, kernel, and proxyType are all separate read functions returning different data types, while ProxyDeposit is an event subscription tool. The descriptions make it impossible to confuse which tool to use for which specific contract query.

Five tools follow a perfect camelCase pattern matching their contract function names (appId, implementation, isDepositable, kernel, proxyType), while ProxyDeposit uses PascalCase for an event. This minor deviation from the dominant pattern prevents a perfect score, but the naming remains highly readable and predictable.

Six tools is reasonable for a smart contract interaction server, providing focused read access to key contract functions and one event subscription. While slightly minimal, each tool serves a distinct purpose without bloat. A perfect score would require more comprehensive coverage of the contract's potential surface.

The toolset is severely incomplete for smart contract interaction. It only provides read functions and event subscription, completely missing write operations (no state modification tools), transaction sending, error handling, or broader contract interaction patterns. This creates significant gaps that will cause agent failures when trying to perform standard blockchain operations.