Skip to main content
Glama

Aave V3 Action

aave_action
Destructive

Perform Aave V3 actions on Base: supply, borrow, repay, or withdraw. Supports auto-wrapping for ETH, 'max' for full balance, and simulate preview.

Instructions

Execute an Aave V3 action on Base: supply, borrow, repay, or withdraw. ETH supply/repay can auto-wrap and ETH withdraw can auto-unwrap; borrowing the ETH market returns WETH. Use 'max' as amount to repay or withdraw the full balance. Set simulate=true for a no-broadcast operation preview.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tokenYesToken symbol (e.g. 'ETH', 'USDC', 'WETH')
actionYesAave action to perform
amountYesAmount (e.g. '100', '0.5', 'max'). Use 'max' for full repay/withdraw.
simulateNoSet true for a no-broadcast operation preview
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Adds important behavioral details beyond annotations: auto-wrap/unwrap, borrowing returns WETH, 'max' uses full balance, simulate preview. Annotations only provide destructiveHint, so description adds value.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three concise sentences, front-loaded with purpose, each sentence adds essential information with no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Fully covers the tool's behavior for an AI agent to use correctly, given the parameter count, annotations, and sibling context. No gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, but description adds nuance (ETH auto-wrap/unwrap, 'max' behavior) that enhances understanding beyond schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it executes Aave V3 actions (supply, borrow, repay, withdraw) on Base, distinguishing it from sibling read-only tools like get_aave_status and get_aave_markets.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides explicit usage hints: auto-wrap/unwrap for ETH, 'max' for full repay/withdraw, simulate for preview. However, does not explicitly state when not to use (e.g., for reading positions).

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Fibrous-Finance/fibx'

If you have feedback or need assistance with the MCP directory API, please join our Discord server