Kaskad Protocol MCP Server

repay

Settle borrowed asset positions on Kaskad Protocol. Use amount -1 to clear the entire outstanding debt.

Instructions

Repay a borrowed asset on Kaskad Protocol. Pass amount=-1 to repay full debt. Testnet only.

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": {
      "asset": "<asset>",
      "amount": "<amount>"
    },
    "name": "repay"
  }
}

Input Schema

Name	Required	Description
`asset`	Yes	Asset symbol
`amount`	Yes	Amount to repay. Use -1 to repay full debt.
`interestRateMode`	No	1 = stable, 2 = variable (default)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A3.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. It states the action and the -1 full-repayment sentinel, but does not disclose side effects, prerequisites like an existing debt, whether repayment is partial or full beyond the sentinel, or what the transaction outcome/return is.

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?

Three short sentences with no fluff. The action is front-loaded, the critical -1 behavior is included, and the testnet restriction is stated. Every sentence earns its place.

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

Completeness3/5

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

The description plus schema is sufficient for a basic call: asset, amount, -1 behavior, and testnet-only. But with no annotations and no output schema, it lacks detail on return values, failure modes, or required preconditions for a state-changing DeFi operation.

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 description coverage is 100%, so the input schema already documents asset, amount, and interestRateMode. The description repeats the -1 full-debt behavior but adds no new parameter meaning beyond the schema.

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 and resource: 'Repay a borrowed asset on Kaskad Protocol.' It clearly distinguishes this from sibling tools like supply, borrow, and withdraw, and adds the useful environment qualifier 'Testnet only.'

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?

The intended use is clear: repay a borrowed asset. The 'Testnet only' note is an explicit environment restriction. However, it does not name alternatives or describe when not to use this tool beyond the testnet limitation.

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

Deploy Server