Skip to main content
Glama

Aave

by com.aave.mcp

Get supported chains

get_chains
Read-only

List chains Aave supports, on v3, v4, or both. A chain carrying 'notServed': true is one this API holds no market on: every market, position and rewards read comes back empty for it, and that emptiness says nothing about the chain itself. Its gateway addresses read 0x0 for the same reason, so do not send a transaction to one. Every chain without the flag has markets to read.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
versionNoProtocol version (default all).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the readOnlyHint and destructiveHint annotations, the description reveals important behavior: notServed chains produce empty market/position/rewards reads, gateway addresses read 0x0, and sending transactions to such chains is unsafe. This is exactly the kind of context annotations cannot express.

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?

The description is three sentences with the core purpose front-loaded and the notServed caveat following in a logical order. Every sentence adds value, and there is no redundant wording.

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 tool with one optional parameter and no output schema, the description covers the key decisions: which version to query, what notServed means, and why gateway transactions should be avoided. It does not spell out the full response shape beyond the notServed and gateway fields, but the low complexity keeps this gap small.

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?

The schema already documents the only parameter fully with an enum and a default value. The description's 'on v3, v4, or both' mirrors the schema rather than adding new semantic detail, so it stays at the baseline for 100% schema coverage.

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 opens with a clear verb and resource: 'List chains Aave supports', then scopes it by protocol version (v3, v4, or both). This gives the agent an unambiguous purpose and naturally separates it from sibling tools like get_markets or get_hubs.

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?

The description gives clear practical guidance: chains with 'notServed': true return empty data and have 0x0 gateway addresses, so transactions should not be sent to them. It does not explicitly compare with alternatives, but the tool's narrow read-only scope makes this omission minor.

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

All Aave toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0
Disambiguation4/5

The tool set splits into clean families (get_ reads, prepare_ transaction builders, direct state-changing verbs) and the descriptions aggressively cross-reference each other to draw explicit boundaries, e.g. get_user_positions vs get_user_summary vs get_user_activity. A few clusters could still prompt misselection: the four get_user_* tools share a naming shape, get_started and get_aave_guide both claim the 'when nothing fits' role, and get_hub_assets vs get_markets both return rate data at different aggregation levels.

Naming Consistency5/5

Every tool follows a verb_noun pattern with a highly predictable convention: get_ for all read operations, prepare_ for every unsigned-transaction builder, and direct imperatives (cancel_order, submit_signed_order, preview_action) for the rest. search_governance_proposals is the only read not named get_, but search_ is semantically apt for full-text lookup. The get_/ prepare_ split is instantly legible across all 40 tools.

Tool Count2/5

40 tools is well past the 25+ 'too many' threshold, and even Aave's genuinely wide scope (v3 and v4 lending, governance, sGHO, rewards, intent orders) does not fully justify the surface. get_started and get_aave_guide overlap as guidance entry points, the three history tools and the get_user_* cluster add near-duplicate reads, and the paragraph-long descriptions compound the agent's context burden. Most tools earn their place individually, but the set would be stronger consolidated to roughly 25-30 tools.

Completeness4/5

Core workflows are fully covered with no dead ends: preview_action simulation, prepare_action and prepare_set_* builders, get_transaction_processed polling, plus the complete order lifecycle (quote, prepare, submit, status, cancel) and sGHO/rewards coverage. Minor gaps remain: governance is read-only with no way to cast a vote, the server cannot read a stkGHO balance or cooldown state for the migration flow, and there is no stkAAVE staking surface. These are workaroundable, and the v3/v4 dual-version handling is unusually thorough.

Resources