Skip to main content
Glama

Aave

by com.aave.mcp
OverviewDiscussionsAdmin

Get APY history

get_apy_history
Read-only

Historical supply or borrow APY for a reserve over time, on v3 or v4. Returns a time-series of {date, apyPct}, where apyPct is a percent ('3.32' means 3.32%). Each point is an average over its sampling interval, and the interval widens with the window (hourly for 'day', coarser above that), so a series is not directly comparable to the instantaneous rate from get_reserve_details. Use get_markets first for the reserveId (v4) or market+token (v3). When comparing v3 against v4 for the same asset (a migration decision), read the history on both sides: a spot-rate gap can be one side's momentary spike.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideNoWhich rate (default supply).
tokenNov3 only: underlying token address.
marketNov3 only: market pool address (from get_markets).
windowNoTime window (default week).
chainIdNov3 only: chain id (positive integer).
versionNoOptional: inferred from the reserve selector ('reserveId' is v4, 'market'+'token'+'chainId' is v3). Send it to be explicit, or if you somehow set both.
reserveIdNov4 only: the reserveId from get_markets, copied verbatim.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / version / description
      Previous value: -"Protocol version (v3 or v4; required)."New value: +"Optional: inferred from the reserve selector ('reserveId' is v4, 'market'+'token'+'chainId' is v3). Send it to be explicit, or if you somehow set both."
    • removedInput schema / required
      Removed value: -[
-  "version"
-]
  2. Changed2 schema fields changed
    • removedInput schema / properties / reserve
      Removed value: -{
-  "description": "v4 only: reserveId (from get_markets).",
-  "type": "string"
-}
    • addedInput schema / properties / reserveId
      Added value: +{
+  "description": "v4 only: the reserveId from get_markets, copied verbatim.",
+  "type": "string"
+}
  3. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Annotations already mark it read-only and non-destructive. The description adds meaningful behavioral detail beyond that: the return format (time-series of {date, apyPct}), the meaning of apyPct as a percent, the averaging semantics per sampling interval, and the warning that series are not directly comparable to instantaneous rates. No contradiction 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?

The description is appropriately sized—every sentence carries information: purpose, return format, sampling semantics, usage prerequisite, and migration caveat. It is front-loaded with the core purpose and structured logically, with no redundant or filler content.

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 tool with 7 parameters and a v3/v4 split, the description covers everything an agent needs: how to obtain the required identifiers, which parameters apply to which version, the return format (no output schema, so this is essential), and the comparison caveat. Nothing critical 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 description coverage is 100%, so the baseline is 3. The description adds value by explaining the v3/v4 selector relationship (reserveId vs market+token+chainId) and advising to use get_markets first, which helps agents assemble the correct parameter set. It doesn't detail every parameter, but the schema already does, so this exceeds the baseline.

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 states a specific action (get historical APY) on a specific resource (a reserve's supply or borrow rate), scoped to v3 or v4, and explicitly distinguishes itself from the instantaneous rate tool get_reserve_details. The verb-resource combination is clear and unambiguous.

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 gives concrete prerequisites ('Use get_markets first for the reserveId (v4) or market+token (v3)') and explains when to use this tool versus the alternative (spot-rate comparison with get_reserve_details, and migration comparison guidance). The when-to-use is explicit and actionable.

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