Skip to main content
Glama
Sign In
Graph AAVE MCP

Graph AAVE MCP

by PaulieB14
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_v4_swap_quote

Get a read-only swap price quote from Aave V4 with MEV protection via CoW Protocol. Returns pricing, fees, and slippage without API key.

Instructions

Get a read-only swap price quote from Aave V4 (powered by CoW Protocol with MEV protection). Returns pricing, fees, and slippage. 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": {
      "sellTokenAddress": "<sellTokenAddress>",
      "buyTokenAddress": "<buyTokenAddress>",
      "sellAmount": "<sellAmount>",
      "userAddress": "<userAddress>"
    },
    "name": "get_v4_swap_quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainIdNoChain ID
sellAmountYesAmount to sell (human-readable, e.g. '100.5')
userAddressYesUser's wallet address
buyTokenAddressYesToken to buy (ERC-20 address)
sellTokenAddressYesToken to sell (ERC-20 address)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv3.0.0

TDQS

A4.2/5.0
Behavior4/5

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

Discloses read-only nature and 'No API key needed'. Does not mention any rate limits or potential side effects, but none are expected for a read-only quote. Adds MEV protection detail.

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 front-load the purpose and key details. No unnecessary words; every sentence adds value.

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?

Mentions return of 'pricing, fees, and slippage' but no output schema. Sufficient for a read-only query, but could detail the output structure more.

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 each parameter has clear descriptions in the schema. The description adds no additional parameter context beyond what the schema already provides.

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?

Clearly states the verb 'Get', the resource 'swap price quote', and the source 'Aave V4 (powered by CoW Protocol)'. Distinguishes from sibling tools like get_v4_reserves or get_v4_user_summary that deal with different operations.

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?

Mentions 'No API key needed', implying simple access. However, lacks explicit guidance on when to use this vs. alternatives like find_best_rates or when not to use it.

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