synthetix-mcp

Every tool has a clearly distinct purpose with no ambiguity. Read functions (e.g., balanceOf, decimals) are separate from write functions (e.g., approve, transfer) and events (e.g., Approval, Transfer), each targeting specific contract methods or events. Overlap is minimal, as tools correspond directly to unique contract functionalities.

Mostly consistent with minor deviations. The majority of tools use camelCase (e.g., acceptOwnership, balanceOf) matching common smart contract naming conventions. However, events like OwnerChanged and TargetUpdated use PascalCase, creating a slight inconsistency. Overall, the naming is readable and follows predictable patterns for the domain.

Borderline, as 22 tools feel heavy for a single contract interface but are reasonable given the comprehensive coverage of ERC-20-like functions, ownership management, and proxy features. It includes many read-only calls and events, which might be excessive for typical agent use but aligns with exposing full contract capabilities.

Complete coverage for the domain of a Synthetix-like contract, including ERC-20 functions (balanceOf, transfer, approve), ownership management (owner, nominateNewOwner), proxy features (target, setTarget), and events. No obvious gaps exist; agents can perform full CRUD/lifecycle operations and monitor state changes without dead ends.