hyperliquid-mcp

The two tools have clearly distinct purposes: execute_exchange handles all trading and account operations (actions), while query_info handles all information retrieval (queries). There is no overlap in functionality, making it easy for an agent to select the correct tool based on the intended operation.

Both tool names follow a consistent verb_noun pattern (execute_exchange and query_info), using clear verbs that describe their core functions. The naming is predictable and readable, with no deviations in style or convention.

With only 2 tools, the server feels too thin for its apparent scope, which includes trading, account management, market data, and staking operations. While the tools are unified endpoints, a typical MCP server for such a domain would benefit from more granular tools (e.g., 5-10) to better guide agents and reduce complexity in request handling.

The tools cover a wide range of operations through unified endpoints, including CRUD-like actions (place/cancel orders, transfer funds) and comprehensive queries (market, user, account data). Minor gaps might exist in specialized operations not listed, but core workflows for trading and information retrieval are well-supported, allowing agents to work effectively.