Skip to main content
Glama
Sign In
lends-mcp-server

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Math Health Factor

lends_math_health_factor
Read-onlyIdempotent

Calculate a position's health factor in basis points to assess liquidation risk, returning null when there is no debt.

Instructions

Calculate health factor in basis points; returns null when debt is zero.

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": {
      "valueLeusd": "<valueLeusd>",
      "debtLeusd": "<debtLeusd>",
      "liquidationThresholdBps": "<liquidationThresholdBps>"
    },
    "name": "lends_math_health_factor"
  }
}

Input Schema

NameRequiredDescriptionDefault
debtLeusdYes
valueLeusdYes
liquidationThresholdBpsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Beyond the readOnly and idempotent annotations, the description discloses an important edge-case behavior: it returns null when debt is zero. This is useful behavioral context that is not visible in the schema or 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?

The description is a single, compact sentence that front-loads the core purpose and adds a key edge-case note. Every word earns its place.

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 straightforward 3-parameter math function with no output schema, the description is mostly complete: it states the output scale and the null behavior. However, it does not clarify parameter semantics, so an agent without DeFi domain knowledge may still be uncertain about inputs.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the meaning, units, or relationship of valueLeusd, debtLeusd, or liquidationThresholdBps. The parameter names are somewhat self-explanatory, but the description adds no semantic value beyond them.

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 clearly states the tool's function: calculating health factor in basis points. It is specific about the resource and unit, though it does not explicitly differentiate itself from the sibling lends_math_* tools.

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?

The description implies usage: use this tool when you need a health factor calculation. However, it provides no explicit guidance about when to prefer it over alternatives or any exclusions, leaving the agent to infer from the function name and context.

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

Deploy Server

Other Tools