SiteCheck Crypto & Finance

Aave v3 Ethereum main-market reserves: supply and borrow

crypto_aave_lending_markets

Read-only

Aave v3 Ethereum main-market reserves: supply and borrow APY, utilization, max LTV, liquidation threshold, supply/borrow caps status, frozen/paused flags, total supplied and available liquidity. Filter by symbol, or get the first 20 reserves. Ethereum main market only. Related tools on this server, for a different need: crypto_dydx_chain_markets when you need dYdX v4 perpetual market for one ticker: status, oracle; finance_pendle_finance_markets_v2 when you need Pendle Finance active yield markets on Ethereum: name. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "crypto_aave_lending_markets"
  }
}

Input Schema

Name	Required	Description	Default
`symbol`	No	Reserve token symbol, e.g. USDC, WETH (optional; default: first 20 reserves)

Output Schema

Name	Required	Description	Default
`count`	No
`market`	No
`source`	No
`chainId`	No
`reserves`	No
`checkedAt`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A4.2/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds genuinely useful operational context that annotations cannot convey: a $0.002 USDC-per-successful-call charge via x402 on Base/Solana/Arc, and that failed calls are not billed — a real cost decision input for an agent. It omits data freshness/caching, but the pricing disclosure is a meaningful bonus.

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?

Front-loaded with the resource and its fields, then defaults, then alternatives, then cost — a sensible order. The long comma-separated field enumeration and the pricing sentence make it denser than ideal, but no sentence is filler given the cost and routing information it carries.

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?

An output schema exists, so return-value shape needn't be described; annotations cover the read-only profile; the sole parameter is fully documented. The description fills the remaining gaps an agent needs before calling — market scope, default fallback, billing model, and no-charge-on-failure behavior.

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

Parameters3/5

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

Schema coverage is 100% and the single parameter already documents 'Reserve token symbol, e.g. USDC, WETH (optional; default: first 20 reserves)'. The description restates the same default and adds only the market-scope constraint, so it adds little beyond the schema. Baseline 3 applies when the schema does the work.

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 names a specific protocol, version, chain, and resource (Aave v3 Ethereum main-market reserves) and then enumerates exactly what is returned: supply/borrow APY, utilization, max LTV, liquidation threshold, caps, frozen/paused flags, totals. An agent can distinguish this from a generic 'market stats' tool without opening the schema.

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 concrete selection guidance: filter by symbol, or take the default first 20 reserves, and it states the scope exclusion 'Ethereum main market only'. It also explicitly routes to two named alternatives with the condition that selects them, though those alternatives (dYdX perps, Pendle) are cross-domain rather than true substitutes; closer siblings such as crypto_compound_market_stats go unmentioned.

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

All SiteCheck Crypto & Finance tools Inspect

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

Need Help?