Kaskad Protocol MCP Server

withdraw

Remove supplied assets from the Kaskad Protocol lending pool. Use amount -1 to clear entire position. Testnet only.

Instructions

Withdraw a supplied asset from the Kaskad Protocol lending pool. Pass amount=-1 to withdraw all. 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": "withdraw"
  }
}

Input Schema

Name	Required	Description	Default
`asset`	Yes	Asset symbol
`amount`	Yes	Amount to withdraw. Use -1 to withdraw all.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A3.8/5.0

Behavior3/5

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

With no annotations, the description carries the behavioral burden. It provides useful context: the testnet-only constraint and the -1 withdraw-all sentinel. But it does not disclose potential side effects, such as health-factor impacts, collateral implications, or failure conditions when withdrawing supplied assets.

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?

Two compact sentences deliver the core action, the critical -1 edge case, and the testnet-only constraint. No filler, and the most decision-relevant information is front-loaded.

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 two-parameter write tool with full schema coverage and no output schema, the description plus schema cover the purpose, special value, and environment. It lacks only explicit guidance about side effects or sequencing with health-factor checks, but the low complexity keeps this from being a major gap.

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%, and both asset and amount are clearly documented there. The description repeats the -1 sentinel already present in the schema, so it adds no new parameter meaning beyond emphasizing an edge case.

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 states a precise verb ('Withdraw'), a specific resource ('supplied asset from the Kaskad Protocol lending pool'), and a special behavior (amount=-1 means withdraw all). This clearly differentiates it from siblings like supply, borrow, repay, and unstakeKSKD.

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 through 'Withdraw a supplied asset' and adds the important environment note 'Testnet only.' However, it does not explicitly contrast with alternatives such as repay or unstakeKSKD, nor state when not to use it, leaving some inference to the agent.

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

Deploy Server