Graph AAVE MCP

get_aave_repays

Get AAVE repayment events for any chain, user address, or asset. Returns repayer, asset, amount, and timestamp.

Instructions

Use this when the user asks about AAVE debt repayment activity — 'Show me recent repayments on Ethereum', 'Has address 0x... repaid any debt?', 'What assets are being repaid most on Arbitrum?', 'Show USDC repay history'. Returns repay events with: repayer address, asset, raw amount, and timestamp. Divide amount by 10^decimals for human-readable value.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "chain": "<chain>"
    },
    "name": "get_aave_repays"
  }
}

Input Schema

Name	Required	Description
`chain`	Yes	Chain identifier
`first`	No	Number of repay events to return (1–100, default 20)
`userAddress`	No	Optional: filter by repayer address (0x...)
`reserveSymbol`	No	Optional: filter by asset symbol (e.g. USDC, WETH, DAI)

Schema Changelog

Changes observed during successful MCP inspections.

Addedv3.0.0Apr 30, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Describes output fields (repayer address, asset, amount, timestamp) and gives transformation guidance (divide by decimals). No annotations provided, so description carries full burden.

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?

Two sentences: first gives usage with examples, second describes output. No unnecessary information.

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

Completeness4/5

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

Covers usage, parameters, and output. Lacks details on ordering or pagination, but the schema provides default and max values.

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?

Adds context beyond schema by explaining how parameters filter repay events and mentions specific asset symbols. Also clarifies amount post-processing.

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 is for AAVE debt repayment activity with specific example queries, distinguishing it from related tools like get_recent_borrows or get_aave_liquidations.

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?

Explicitly says when to use and provides example queries, but does not mention when not to use or list alternatives.

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

Deploy Server