Skip to main content
Glama
Sign In
Graph AAVE MCP

Graph AAVE MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v4_user_borrows

Fetch Aave V4 borrow positions for any EVM wallet, returning principal, debt, and interest. No API key needed.

Instructions

Get a user's Aave V4 borrow positions with principal, debt, interest. No API key needed.

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": {
      "userAddress": "<userAddress>"
    },
    "name": "get_v4_user_borrows"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoFilter by chain ID
userAddressYesEVM wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description must cover behavioral traits. It states it returns 'principal, debt, interest' but omits details like authentication requirements, rate limits, or that it is a read-only operation.

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?

Extremely concise with two sentences that front-load the purpose and key differentiator (no API key). Every word adds value.

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

Completeness3/5

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

Given no output schema, the description partially explains return values (principal, debt, interest) but lacks structural details. For a simple tool it is adequate but could be more complete.

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%, so the schema already describes both parameters adequately. The description does not add new semantic information beyond what is in the schema.

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 specifies the tool retrieves a user's Aave V4 borrow positions, listing key data points (principal, debt, interest). This distinguishes it from sibling tools like get_v4_user_supplies or get_v4_user_positions.

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

Usage Guidelines3/5

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

No explicit guidance on when to use this tool versus alternatives. The note 'No API key needed' provides some context but no comparison with siblings or conditions for use.

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

Deploy Server

Other Tools