wormhole-mcp

Many tools have overlapping purposes, causing significant ambiguity. For example, multiple tools like 'find_vaa_by_id', 'find_duplicated_vaa_by_id', and 'get_transaction_by_id' all seem to retrieve VAA-related data with unclear distinctions. Similarly, governor-related tools (e.g., 'governor_notional_available_by_chain', 'governor_max_notional_available_by_chain') have overlapping scopes, making it hard for an agent to choose the right one without deep domain knowledge.

The naming is mixed but somewhat readable. There are consistent patterns within groups (e.g., 'find_' prefix for VAA/observation queries, 'governor_' prefix for governor data), but overall conventions vary: some use snake_case (e.g., 'api_v1_native_token_transfer_activity'), others use simpler forms (e.g., 'circulating_supply'), and there's no uniform verb-noun structure. This inconsistency can confuse agents but doesn't render the set unreadable.

With 73 tools, the count is excessive for a single server, indicating poor scoping. While Wormhole is a complex blockchain protocol, the tool surface feels bloated with many overlapping or highly specialized functions (e.g., multiple governor notional tools). A more curated set of 15-30 tools would likely suffice, making this overly heavy and difficult for agents to navigate efficiently.

The tool set appears highly complete for the Wormhole domain, covering VAAs, transactions, governor data, token transfers, and protocol analytics. There are discovery tools, CRUD-like operations for queries, and monitoring functions. Minor gaps might exist in mutation operations (e.g., creating or updating data), but given the exploratory/read-only nature implied, coverage is thorough for data retrieval and analysis.