Skip to main content
Glama

Liquidation risk

liquidation_risk
Read-only

Monitor Solana lending pools approaching liquidation. Tracks utilization rates across Kamino, MarginFi, Drift, Solend, Save, and Mango. Returns risk levels (CRITICAL/HIGH/MEDIUM/LOW), market stress indicator, and per-protocol summaries. Costs $0.005 USDC per call.

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

Input Schema

NameRequiredDescriptionDefault
assetNoFilter by asset symbol (e.g. 'USDC', 'SOL')
protocolNoFilter by protocol (e.g. 'kamino', 'marginfi', 'drift')
riskLevelNoMinimum risk level: LOW, MEDIUM, HIGH, CRITICAL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

The description adds genuinely useful context beyond the annotations: the return shape (risk levels, market stress indicator, per-protocol summaries) and, importantly, a $0.005 USDC per-call cost. It omits the default behavior when no filters are supplied (presumably all pools) and any rate limits, keeping it short of a 5.

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?

Four tight sentences with the core purpose front-loaded, then coverage, then outputs, then cost. No filler; the cost sentence is last but still relevant.

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?

With no output schema, the description appropriately summarizes what is returned and adds cost. All three optional filters are schema-documented, so the definition is nearly complete; only default unfiltered behavior and payment/auth mechanics remain unstated.

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%, so the schema already documents asset, protocol, and riskLevel. The description's mention of the CRITICAL/HIGH/MEDIUM/LOW ordering reinforces the riskLevel threshold semantics, but that mapping is already present in 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?

States a specific verb+resource ('Monitor Solana lending pools approaching liquidation') and enumerates the covered protocols (Kamino, MarginFi, Drift, Solend, Save, Mango). An agent can distinguish it from generic lending_rates or history-oriented recent_liquidations, though no sibling is named explicitly.

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 implied by 'approaching liquidation' and the filter parameters, but there is no explicit guidance on when to prefer this over recent_liquidations or lending_rates, nor any stated preconditions (e.g. wallet/payment setup for the USDC cost).

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