Skip to main content
Glama

Ellimist

Aave V3 USDC rates

data_defi_aave_rates
Read-only

Use this to get the current USDC lending (supply) APR and variable borrow APR on Aave V3 (Base or Ethereum), read from the Aave pool contract at a finalized block. Price: $0.005 USDC per call via x402 (no account). Not charged if it fails.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "data_defi_aave_rates"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNobase

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Beyond readOnlyHint/openWorldHint, it discloses the data provenance (Aave pool contract), freshness semantics (finalized block), the access model (x402 micropayment, no account), and the billing behavior on failure (not charged). That is exactly the auth/cost/behavioral 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?

Three short sentences, each carrying distinct information (what, where from, cost) with the core purpose front-loaded. No filler or redundancy.

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 one-parameter read-only tool with annotations and no output schema, the definition covers purpose, source, chain scope, freshness, and cost. It stops short of describing the return shape or units (percent vs. decimal, whether both rates are always present), a minor gap given there is no output schema.

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 description coverage is 0%, and the only parameter, chain, is mentioned in prose as "Base or Ethereum", which roughly mirrors the enum already in the schema without adding format or default guidance. For a single self-evident enum parameter this is adequate but adds little meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: get the USDC supply APR and variable borrow APR on Aave V3, scoped to Base or Ethereum, read from the pool contract at a finalized block. The purpose is unambiguous, though it never names or contrasts any sibling tool (e.g., data_defi_yield_vs_tbill), so an agent must infer the distinction.

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?

It opens with explicit when-to-use framing ("Use this to get the current USDC lending (supply) APR and variable borrow APR") and constrains the context to Aave V3 on two chains. There are no explicit when-not conditions or named alternatives, which keeps it short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources