Aave transaction preparation

Every tool named below comes from Aave's MCP server, https://mcp.aave.com. If get_markets is not available, add it first: claude mcp add --transport http aave https://mcp.aave.com (Claude Code), codex mcp add aave --url https://mcp.aave.com (Codex), or point any other MCP client at the URL.

Non-custodial: every tool here returns an unsigned transaction for the user's own wallet to sign. Say what a prepared transaction will do once signed, and that nothing has been sent.

The chain is discover → inspect → simulate → build, then hand over unsigned.

Steps

1. Discover — get_markets with symbols, and user set to the sender, in this session even when a market looks familiar: selectors (v4 reserveId; v3 market + token + chainId) are deployment-specific and cannot be recalled. The user rows say what this wallet can actually supply or borrow before anything is built.
2. Inspect — get_user_summary for what the wallet already owes and how much room it has, and get_reserve_details where the reserve's own parameters bear on the action. A borrow or a withdraw sized without this is a guess.
3. Simulate — preview_action with the exact parameters you intend to build. Mandatory before every borrow and withdraw; run it for supply and repay too. An error-level warning means the action cannot succeed as specified: fix the inputs or tell the user, rather than building it.
4. Build — prepare_action with the same selectors and amount. Follow the returned plan in order: an approval step comes before the action, and a sent transaction is confirmed with get_transaction_processed before building one that depends on it.
5. Hand over — show the unsigned transaction, the simulated outcome (the health factor after, for anything touching debt or collateral), and every warning (warning level succeeds but must reach the user). Then stop: signing is the user's move.

Rules