Aave MCP

One asset wherever v4 holds it

get_multichain_asset

Read-only

v4 only. One asset across every v4 chain at once, by symbol: what is supplied and borrowed on each, the rate on each, and a summary naming the best supply rate and the lowest borrow rate anywhere. This is the tool for 'where should I supply USDC' and for 'is this cheaper to borrow somewhere else' - one call rather than reading get_markets per chain. It answers about the asset, not about a wallet. Omit chainId to cover every chain v4 serves, stated under 'chainsCovered'.

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": {
      "symbol": "<symbol>"
    },
    "name": "get_multichain_asset"
  }
}

Input Schema

Name	Required	Description
`symbol`	Yes	Token symbol, e.g. 'USDC'. Case-insensitive.
`chainId`	No	Chain id to restrict to, e.g. 1 for Ethereum. Omit the argument entirely to cover every chain.
`version`	No	Optional, and only 'v4': this tool exists on v4 only.

Schema Changelog

Changes observed during successful MCP inspections.

AddedSep 15, 2026

TDQS

A4.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false; the description adds useful behavioral context beyond them by restricting to v4, explaining that omitting chainId covers every v4 chain, and telling the agent the response includes 'chainsCovered.' There is 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?

Four sentences with no filler. Scope, output content, use cases, alternative routing, boundary, and optional-parameter behavior are all front-loaded, and every sentence adds distinct value.

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?

Even without an output schema, the description names the substantive response components: supplied/borrowed amounts, per-chain rates, best-rate summary, and chainsCovered. It also explains exactly how to invoke the tool, covering selection and behavior well enough for an agent to call it correctly.

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 coverage is 100%, so the baseline is 3; the description earns extra credit by explaining the practical behavior of omitting chainId ('cover every chain v4 serves') and reinforcing that version only accepts v4. This complements rather than merely repeats 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 states a specific verb and resource: 'One asset across every v4 chain at once, by symbol,' and enumerates the outputs (supplied, borrowed, rates, best supply/borrow summary). This clearly distinguishes it from asset-level versus wallet-level tools like get_wallet_balances and per-chain tools like get_markets.

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 explicitly names the use cases ('where should I supply USDC' and 'is this cheaper to borrow somewhere else'), calls out get_markets as the alternative requiring per-chain calls, and states the boundary: 'It answers about the asset, not about a wallet.' This gives an agent clear selection criteria.

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

All Aave MCP tools Inspect

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

Need Help?