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

lends-mcp-server

Official
by LendsProtocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Lends Math Pending Vault Fee

lends_math_pending_vault_fee
Read-onlyIdempotent

Calculate pending vault fees from debt, stability fee APR, and accrual timestamps, using contract-equivalent floor rounding.

Instructions

Calculate projected simple vault fees with contract-equivalent floor rounding.

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": {
      "debt": "<debt>",
      "stabilityFeeAprBps": "<stabilityFeeAprBps>",
      "lastAccrualTs": "<lastAccrualTs>",
      "timestamp": "<timestamp>"
    },
    "name": "lends_math_pending_vault_fee"
  }
}

Input Schema

NameRequiredDescriptionDefault
debtYes
timestampYes
lastAccrualTsYes
stabilityFeeAprBpsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, idempotent, and non-destructive behavior, so the description only needs to add non-obvious behavior. It does so by disclosing the floor-rounding mode and contract-equivalent matching, which tells the agent the calculation is a pure simulation with a specific rounding rule.

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 front-loaded sentence with no filler. Every phrase ('projected', 'simple vault fees', 'contract-equivalent floor rounding') carries a distinct piece of information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and four required math inputs, the description is too thin: it does not explain the return value, the formula, the meaning of the two timestamps, or the units of stabilityFeeAprBps. The annotations cover safety but not the calculation contract an agent needs to invoke it correctly.

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 define any of the four parameters. The names (debt, stabilityFeeAprBps, lastAccrualTs, timestamp) and pattern are somewhat self-explanatory, but the description adds no explicit meaning, units, formula role, or ordering semantics, leaving a material gap for a calculation tool.

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 uses a specific verb ('Calculate') and names a distinct resource ('projected simple vault fees'), plus a defining behavioral detail ('contract-equivalent floor rounding'). This separates it clearly from sibling math tools like health factor or liquidation price by its fee-specific purpose.

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 word 'projected' implies this is for estimating pending/accrued vault fees rather than performing an actual on-chain accrual, giving a rough usage context. However, it never names alternatives (e.g., lends_prepare_accrue_fee) or states explicit when-to-use/when-not-to-use conditions, so guidance is only implied.

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