Skip to main content
Glama

Get markets / reserves

get_markets
Read-only

List Aave markets/reserves (symbol, APY, caps, liquidity) on v3, v4, or both. Chain coverage: omit chainId and every response states the chains it read as 'chainsCovered', plus 'chainsNotCovered' when it read fewer than all of them. 'chainsNotServed', when present, lists chains this API holds no market on: Aave supports the chain, there is nothing here to read, so an empty result for one of them is not an answer about that chain, and asking again returns the same nothing. v4 always covers every chain it serves; v3 covers every chain when you pass 'symbols' and Ethereum alone when you do not, because an unfiltered 21-chain listing is hundreds of kilobytes. So to compare one asset across chains, pass symbols and no chainId. Every rate is a percent ('3.32' means 3.32%), named with a Pct suffix. Do not rank on APY alone: 'suppliable'/'borrowable' (v4), 'availableLiquidity' and 'totalSuppliedUsd' (v3) say whether a rate can actually be entered, and isFrozen / isPaused / supplyCapReached / borrowCapReached appear only when set, so a reserve with none of them is not flagged. Both versions return one row per reserve under 'reserves', carrying supplyApyPct and borrowApyPct together plus canSupply / canBorrow for the sides that are actually open, so the two versions read the same way. On v4 one asset appears once per spoke, so rows are labelled with 'spoke' and 'hub'; spokes sharing a hub share its rate, so identical APYs across rows are expected rather than duplicates. 'canSwapFrom' (v4) says whether that token can be the sell side of a token swap, which is the per-reserve form of what get_swappable_tokens answers per chain. 'quotableAs' (v4) lists the order-quote arguments the reserve can fill: supplySwapTo or borrowSwapTo as get_position_swap_quote's buyReserve, repayWith as get_repay_with_supply_quote's repayWithReserve, leverageDebt and leverageCollateral as get_leverage_quote's debtReserve and collateralReserve. It is absent when the reserve fills none of them.

Input Schema

NameRequiredDescriptionDefault
userNoOptional wallet address (0x, 40 hex). Adds walletBalance, youCanSupply and youCanBorrow to every row, for this wallet, in the same call. Pass it whenever the question is about what someone can actually do rather than what the rates are.
chainIdNoChain id to restrict to, e.g. 1 for Ethereum. Omit the argument entirely to cover every chain.
symbolsNoOptional token symbols to return, e.g. ['USDC','GHO']. Case-insensitive. Strongly preferred when you know the asset: a chain has ~70 reserves and listing them all is a large response.
versionNoProtocol version (default all).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only establish that this is a safe read operation; the description adds substantial behavioral context beyond them, including chain coverage semantics, the v3/v4 coverage asymmetry, empty-result interpretation for 'chainsNotServed', rate units, conditional flags, and v4 spoke/hub row behavior.

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

Conciseness4/5

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

The description is dense and long, but it is front-loaded with the core purpose and every block conveys non-obvious behavior needed to interpret this complex tool without an output schema. It could be easier to scan with bullets, but there is little empty filler.

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?

Given four optional parameters, no output schema, and fairly complex v3/v4 chain and reserve semantics, the description covers the return shape, field meanings, edge cases, and cross-tool field mappings thoroughly. An agent has enough context to call it correctly and interpret the result.

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

Parameters5/5

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

Although schema coverage is already 100%, the description adds non-obvious parameter interactions: 'symbols' expands v3 coverage beyond Ethereum, omitting 'chainId' produces 'chainsCovered'/'chainsNotCovered', and 'user' changes every row with wallet-specific fields. These are meaningful semantics beyond what the schema states.

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 opens with a specific verb and resource ('List Aave markets/reserves') and names the returned fields, versions, and scope. An agent can tell immediately that this is the market/reserve listing tool rather than a details, history, or quote tool.

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?

It gives explicit parameter-driven usage conditions: pass 'symbols' and omit 'chainId' to compare one asset across chains, and pass 'user' when the question is about wallet capabilities. It also warns against ranking on APY alone, but does not explicitly name an alternative tool to use for deeper reserve-level questions.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources