Kaskad Protocol MCP Server

checkHealthFactor

Monitor a wallet's health factor against a threshold and receive alert levels from safe to critical. Returns alert:true when below threshold, enabling automated repay or supply actions in agent monitoring loops.

Instructions

Check a wallet's health factor against a threshold. Returns alert:true if HF is below threshold. Use in agent monitoring loops: call on a cron interval and trigger repay() or supply() when alert:true. Alert levels: safe | warning (below threshold) | danger (HF < 1.2) | critical (HF < 1.05, liquidation imminent).

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": "checkHealthFactor"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Wallet address (0x...) to monitor
`threshold`	No	Health factor threshold to alert below. Default: 1.5. Must be between 1.0 and 10.0.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations, the description carries the behavioral burden. It discloses the boolean alert result, the threshold comparison, and defines alert tiers (safe/warning/danger/critical) with numeric cutoffs. It does not specify the full response shape or error behavior, but the key monitoring semantics are present.

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 definition opens with the core purpose, then return semantics, usage loop, and alert tiers. It is compact and front-loaded, with each sentence adding distinct value; the only minor redundancy is 'warning (below threshold)' after the earlier alert:true statement.

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 read-style monitoring tool with full schema coverage, the description covers purpose, usage loop, threshold behavior, and alert levels. It lacks a formal output schema, but none exists, and the described behavior is sufficient for an agent to invoke and react to it.

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%; both address and threshold already have descriptions, including default and range. The description adds no new parameter-level detail beyond referencing the threshold, so baseline 3 is appropriate.

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 ('Check'), a specific resource ('a wallet's health factor'), and the comparison ('against a threshold'). It also names the alerting behavior, which separates it from read tools like getPosition or getMarkets.

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?

Explicitly prescribes a monitoring loop: call on a cron interval and trigger repay() or supply() when alert:true. This is clear usage context. It doesn't explicitly name exclusions or alternatives, but the intended use case is unambiguous.

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

Deploy Server