Skip to main content
Glama
Sign In

agentforge

by io.github.acarchidi
OverviewDiscussionsAdmin

lending_health

Read-onlyIdempotent

How close a wallet is to liquidation on Aave v3 (Ethereum, Base, Arbitrum, Optimism, Polygon, BNB Chain, Avalanche, Linea, and Sonic in one call): collateral, debt, health factor, status, and how far collateral can fall before liquidation. Free over MCP for 10 calls per day; beyond that the tool returns the pay-per-call x402 endpoint and its price.

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": {
      "address": "<address>"
    },
    "name": "lending_health"
  }
}

Input Schema

NameRequiredDescriptionDefault
chainNoall
addressYesWallet address

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / chain / enum
      Previous value: -[
-  "all",
-  "ethereum",
-  "base",
-  "arbitrum",
-  "optimism",
-  "polygon"
-]New value: +[
+  "all",
+  "ethereum",
+  "base",
+  "arbitrum",
+  "optimism",
+  "polygon",
+  "bsc",
+  "avalanche",
+  "linea",
+  "sonic"
+]
  2. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent, non-destructive, and open-world behavior, so the bar is lower. The description adds genuinely useful behavioral context the annotations cannot: a 10-call-per-day free quota over MCP, and the fact that over quota the tool returns the pay-per-call x402 endpoint and its price rather than failing silently.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and output list are front-loaded, and the quota/payment sentence is a compact, high-value addition. The chain enumeration is long but it is doing real work; only mildly compressible.

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?

There is no output schema, so the description carries the burden of describing return content, and it does: collateral, debt, health factor, status, and liquidation buffer. Combined with the quota behavior, it is nearly complete; only the chain='all' aggregation semantics and the no-position case are unaddressed.

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 only 50% (chain has an enum and default but no description). The description compensates by enumerating the supported chains, which clarifies what chain='all' actually aggregates into a single response. It does not clarify whether results are per-chain or merged when chain='all' is used.

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?

States a specific verb-equivalent ('how close a wallet is to liquidation') plus a precise resource (Aave v3 positions) and enumerates the outputs: collateral, debt, health factor, status, liquidation distance. The scope is narrow enough that it is hard to confuse with siblings such as wallet_safety or pool_snapshot.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: the agent can infer this is the call for Aave liquidation-risk checks, and 'in one call' hints at using the chain='all' default. There is no explicit when-to-use versus when-to-use-a-sibling guidance and no prerequisites (for example, a wallet with no Aave position).

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

All agentforge toolsInspect
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