Kaskad Protocol MCP Server

getStakingInfo

Retrieve a wallet's staking vault details, including stKSKD balance, KSKD balance, and holding duration, to assess its staking position.

Instructions

Get stKSKD vault state for a wallet: stKSKD balance, KSKD wallet balance, holding duration.

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": {
      "address": "<address>"
    },
    "name": "getStakingInfo"
  }
}

Input Schema

Name	Required	Description	Default
`address`	Yes	Wallet address (0x...) to check staking info for

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 15, 2026

TDQS

A3.6/5.0

Behavior3/5

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

No annotations are provided, so the description carries the behavioral burden. The verb 'Get' plus 'state' strongly implies a non-mutating read operation, but the description does not explicitly confirm there are no side effects, permission requirements, or special failure cases.

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 entire description is one compact, front-loaded sentence with a colon-separated list of outputs. Every word adds information and there is no filler.

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 low-complexity, single-parameter read tool, the description is nearly complete: it names the resource, the scope, and the returned fields. Lacking only explicit non-mutation confirmation and units for holding duration, both minor for this simple case.

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?

The input schema already documents the sole address parameter to 100% coverage. The description adds no new meaning about the parameter beyond the schema, so the baseline 3 applies.

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 uses a specific verb-resource pair ('Get stKSKD vault state') and enumerates the exact data returned, so an agent can identify what this tool does. It does not explicitly contrast it with siblings like getPosition, but the phrase 'for a wallet' and the listed staking-specific fields are sufficiently distinguishing.

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 wording implies a read-only query for a wallet's staking status, which is a clear use case. However, it never states when to choose this over likely alternatives (e.g., getPosition or getUserRewards) or any exclusions.

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

Deploy Server