Teardrop

Get Lending Rates

get_lending_rates

Read-only

Get current on-chain lending supply/borrow rates for expanded Aave v3 reserves and Compound v3 markets on Ethereum or Base. Returns per-asset APY snapshots and Compound utilization where available. Useful for protocol-specific stablecoin yield comparisons (e.g., USDC on Aave vs Compound).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`assets`	No	Optional asset-symbol filter (e.g., ['USDC','DAI']). Case-insensitive. Max 20 symbols.
`chain_id`	No	Chain ID (1=Ethereum, 8453=Base).
`protocol`	No	Protocol to query: 'aave-v3', 'compound-v3', or 'all'.	all

Output Schema

TableJSON Schema

Name	Required	Default
`note`	No	On-chain lending market snapshot at data_block_number. Aave rates are derived from ProtocolDataProvider.getReserveData (ray-scaled). Compound rates are derived from Comet getUtilization/getSupplyRate/getBorrowRate (per-second 1e18-scaled), annualized to APY.
`rates`	Yes
`errors`	No
`chain_id`	Yes
`protocol`	Yes
`data_block_number`	Yes

Schema Changelog

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

Changed11 schema fields changedAug 14, 2026

removedInput schema / additionalProperties
```
Removed value: -false
```
addedInput schema / properties / assets / title
```
Added value: +"Assets"
```
addedInput schema / properties / chain_id / title
```
Added value: +"Chain Id"
```
addedInput schema / properties / protocol / title
```
Added value: +"Protocol"
```

addedInput schema / title

Added value: +"mcp_get_lending_ratesArguments"

addedOutput schema / $defs

Added value: +{
+  "LendingRateEntry": {
+    "properties": {
+      "asset_symbol": {
+        "title": "Asset Symbol",
+        "type": "string"
+      },
+      "borrow_apy_pct": {
+        "title": "Borrow Apy Pct",
+        "type": "number"
+      },
+      "chain_id": {
+        "title": "Chain Id",
+        "type": "integer"
+      },
+      "market_name": {
+        "title": "Market Name",
+        "type": "string"
+      },
+      "protocol": {
+        "enum": [
+          "aave-v3",
+          "compound-v3"
+        ],
+        "title": "Protocol",
+        "type": "string"
+      },
+      "source": {
+        "const": "on-chain",
+        "default": "on-chain",
+        "title": "Source",
+        "type": "string"
+      },
+      "supply_apy_pct": {
+        "title": "Supply Apy Pct",
+        "type": "number"
+      },
+      "utilization_pct": {
+        "anyOf": [
+          {
+            "type": "number"
+          },
+          {
+            "type": "null"
+          }
+        ],
+        "default": null,
+        "title": "Utilization Pct"
+      }
+    },
+    "required": [
+      "protocol",
+      "chain_id",
+      "market_name",
+      "asset_symbol",
+      "supply_apy_pct",
+      "borrow_apy_pct"
+    ],
+    "title": "LendingRateEntry",
+    "type": "object"
+  }
+}

addedOutput schema / properties / rates / items / $ref
```
Added value: +"#/$defs/LendingRateEntry"
```

removedOutput schema / properties / rates / items / properties

Removed value: -{
-  "asset_symbol": {
-    "title": "Asset Symbol",
-    "type": "string"
-  },
-  "borrow_apy_pct": {
-    "title": "Borrow Apy Pct",
-    "type": "number"
-  },
-  "chain_id": {
-    "title": "Chain Id",
-    "type": "integer"
-  },
-  "market_name": {
-    "title": "Market Name",
-    "type": "string"
-  },
-  "protocol": {
-    "enum": [
-      "aave-v3",
-      "compound-v3"
-    ],
-    "title": "Protocol",
-    "type": "string"
-  },
-  "source": {
-    "const": "on-chain",
-    "default": "on-chain",
-    "title": "Source",
-    "type": "string"
-  },
-  "supply_apy_pct": {
-    "title": "Supply Apy Pct",
-    "type": "number"
-  },
-  "utilization_pct": {
-    "anyOf": [
-      {
-        "type": "number"
-      },
-      {
-        "type": "null"
-      }
-    ],
-    "default": null,
-    "title": "Utilization Pct"
-  }
-}

removedOutput schema / properties / rates / items / required

Removed value: -[
-  "protocol",
-  "chain_id",
-  "market_name",
-  "asset_symbol",
-  "supply_apy_pct",
-  "borrow_apy_pct"
-]

removedOutput schema / properties / rates / items / title
```
Removed value: -"LendingRateEntry"
```
removedOutput schema / properties / rates / items / type
```
Removed value: -"object"
```

First observedJul 9, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true, so the description adds value by disclosing the return format: 'per-asset APY snapshots and Compound utilization where available.' It also includes the caveat 'where available,' which clarifies behavior when data may be incomplete. No contradictions 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?

Three sentences, each with a specific purpose: what it returns, return details, and a use-case example. No fluff or redundant information. Front-loaded with the primary action ('Get current on-chain lending supply/borrow rates').

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?

The tool has an output schema, so return values need not be explained, but the description still mentions APY snapshots and utilization, which helps. The description covers the protocols, chains, and a concrete use case, making it complete for a read-only list-style tool with well-documented parameters and annotations.

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% (all parameters have descriptions), so the baseline is 3. The description adds context about protocol and chain coverage ('Aave v3 reserves and Compound v3 markets on Ethereum or Base') but does not add meaning for the assets filter or chain_id beyond what the schema already provides. The description does not compensate for any parameter gaps because there are none.

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 ('Get') with a clear resource ('on-chain lending supply/borrow rates') and explicitly scopes it to 'expanded Aave v3 reserves and Compound v3 markets on Ethereum or Base.' It also distinguishes from siblings like get_yield_rates by emphasizing protocol-specific lending rates, not general yields.

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 indicates when to use this tool: 'Useful for protocol-specific stablecoin yield comparisons (e.g., USDC on Aave vs Compound).' This provides clear context, but it does not explicitly mention sibling tools as alternatives or state when NOT to use it. No exclusions are given.

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

All Teardrop tools Inspect

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

A3.7/5.0

Disambiguation3/5

Most tools target distinct data sources, but several near-duplicates exist: get_token_approvals/get_wallet_approvals, get_defi_positions/get_wallet_positions, and get_wallet_portfolio/get_eth_balance. The descriptions do cross-reference and clarify the differences, so an agent can disambiguate with effort, but names alone are not enough.

Naming Consistency4/5

The dominant get_<noun> pattern is clear and nearly all names use lowercase snake_case with verb-first conventions. A few tools like calculate, record_predictions, http_fetch, and web_search break the get_ pattern, but the overall style remains predictable.

Tool Count2/5

34 tools is excessive for a single server, even for a broad DeFi/onchain analytics domain. The count is inflated by generic utilities such as calculate, count_text_stats, web_search, and http_fetch, plus multiple overlapping data-retrieval endpoints, making the surface hard to scan.

Completeness4/5

The set covers an unusually wide range of domain operations: prices, balances, portfolio/positions, approvals, yields, TVL, DEX quotes/volume, transactions, blocks, gas, ENS, contract reads, and risk assessments. It is view-only by design, so missing write/transaction tools is acceptable; minor gaps like address-based token pricing or transaction simulation are workaround-able.

Resources

Need Help?