metalend

Each tool targets a clearly distinct action or resource: auth, balances, config, deposits, withdrawals, pools, rewards, token metadata, costs, and statuses are all separated. The descriptions explicitly contrast overlapping-seeming tools (e.g., get_balances vs get_bridge_balances, get_config vs get_default_config, prepare_* vs submit_*), leaving little room for misselection.

Every tool uses consistent snake_case with a predictable verb_noun structure: get_*, prepare_*, submit_*, and list_*. The read/prepare/submit lifecycle is reflected uniformly across config, deposit, and withdrawal operations, with no mixed conventions.

Nineteen tools is slightly above the ideal 3-15 range, but the scope is genuinely broad DeFi rebalancer management. Most tools earn their place by separating read/prepare/submit steps and distinct statuses, though some consolidation may be possible.

The surface covers the core lifecycle: authentication, configuration, deposits, withdrawals, balances, pool discovery, rewards, token metadata, costs, and status polling. Minor gaps exist, such as no direct reward-claim execution or transaction history, but these are either explicitly unsupported by the backend or workable around documented flows.