Skip to main content
Glama

Aave

by com.aave.mcp
OverviewDiscussionsAdmin

Get Aave Vaults, or a wallet's shares in them

get_vaults
Read-only

v3 only. Name exactly one of 'user', 'owner' or 'vault', and read that sentence before choosing arguments: 'user' lists every vault that wallet holds shares in and is the portfolio question, 'owner' lists what one curator runs, 'vault' reads a single vault by address and is the only one that also needs 'chainId'. An Aave Vault is an ERC-4626 vault a curator deploys over one v3 reserve, taking a fee on the yield, so its APR is below that reserve's by the fee. Shares in one are an Aave position that no market read returns. There is no catalogue to browse: this API has no "list every vault" call, so a request to find the best vault cannot be answered here - you can only look up vaults whose address, owner or holder you already have. 'aprPct' is already net of 'feePct'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
userNoWallet address (0x, 40 hex) to list its vault positions. Omit the argument entirely when using another selector.
ownerNoCurator address (0x, 40 hex) to list the vaults it owns. Omit the argument entirely when using another selector.
vaultNoVault contract address (0x, 40 hex) to read one vault. Needs 'chainId'. Omit the argument entirely when using another selector.
cursorNo'nextCursor' from a previous call, to continue a 'user' or 'owner' listing. Omit the argument entirely for the first page.
chainIdNoChain the vault is on, e.g. 1 for Ethereum.
versionNoOptional, and only 'v3': this tool exists on v3 only.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / cursor
      Added value: +{
+  "description": "'nextCursor' from a previous call, to continue a 'user' or 'owner' listing. Omit the argument entirely for the first page.",
+  "type": "string"
+}
  2. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark readOnly and non-destructive, and the description adds valuable behavioral context beyond that: v3-only restriction, exclusive selectors, chainId requirement for vault, vault domain semantics (ERC-4626, fee on yield, APR net of fee), and the absence of a browse-all endpoint. No contradictions with annotations.

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?

Every sentence adds crucial information: the opening line gives the critical exclusivity rule, followed by mode definitions, domain context, and negative scope. It is dense but tightly structured with no filler or 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?

For a 6-parameter tool with no required parameters and no output schema, the description fully covers the calling pattern (selectors, chainId condition), the domain meaning, and a key output semantic (aprPct net of fee). It also anticipates a likely misuse (finding best vault) and preempts it. Nothing an agent needs to call it correctly is missing.

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%, so baseline is 3; the description adds extra meaning by enforcing exactly-one-of user/owner/vault, stating that only vault requires chainId, and clarifying aprPct/feePct relationship. However, it leaves some parameter details like cursor pagination to the schema, which is acceptable given full schema coverage.

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 the tool gets Aave vaults or a wallet's shares, and enumerates three distinct selector modes ('user', 'owner', 'vault') with explicit scope for each. This distinguishes it from sibling tools like get_markets or get_reserve_details, and explicitly states what it cannot do (no list-every-vault catalogue).

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

Usage Guidelines5/5

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

It explicitly instructs to name exactly one of the three selectors and when to use each mode ('portfolio question', 'what one curator runs', 'single vault'). It also gives a negative usage rule: because there is no catalogue, it cannot answer 'best vault' requests and requires known addresses, which tells the agent when not to use it.

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

All Aave toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources