Skip to main content
Glama
Sign In
Graph AAVE MCP

Graph AAVE MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v4_user_balances

Retrieve a user's cross-chain token balances in Aave V4, showing the highest supply APY and lowest borrow APY per token without needing an API key.

Instructions

Get a user's cross-chain token balances in Aave V4 with highest supply APY and lowest borrow APY per token. 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_balances"
  }
}

Input Schema

NameRequiredDescriptionDefault
userAddressYesEVM wallet address (0x...)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations, the description carries full burden. It states 'No API key needed', which is useful, but lacks details on read-only behavior, rate limits, or response structure. The APY mention adds some behavioral context.

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 short, front-loaded sentences with no wasted words. Key information (verb, resource, special features, auth requirement) is conveyed efficiently.

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?

For a simple one-parameter tool, the description covers the core functionality and a notable behavioral trait (no API key). It does not explain output format or limitations, but the tool's complexity is low.

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% with a clear description for userAddress. The description does not add extra parameter semantics beyond the schema, so baseline of 3 is appropriate.

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 verb 'Get' and the resource 'user's cross-chain token balances in Aave V4', and adds differentiation by mentioning 'highest supply APY and lowest borrow APY per token'. It distinguishes from sibling tools like get_v4_user_positions or get_v4_user_summary.

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?

The description implies usage for retrieving balances with APY highlights but does not explicitly state when to use over siblings or when not to use. No alternatives or exclusion criteria are mentioned.

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