Crank Protocol

unstake_lst

Destructive

Unstake an LST back to SOL (non-custodial).

lst_token is a mint (mSOL/jitoSOL/bSOL); amount in base units. mSOL routes via Marinade, others via the Sanctum router. Returns an UNSIGNED base64 tx. The technology service fee is charged on the unstaked-LST notional past the daily free tier (x402 payment_header).

idempotency_key (optional): a client-generated UUID. Retrying with the same key + same args replays the original result instead of re-unstaking. Reuse the SAME key across the build call and its signed_transaction completion call -- see liquid_stake; the two legs dedupe independently, so this never raises IDEMPOTENCY_CONFLICT.

signed_transaction / verify (two-phase execution): see liquid_stake -- re-call with the signed tx and Crank broadcasts it, confirms it on-chain, and re-reads the LST + SOL balances.

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": {
      "lst_token": "<lst_token>",
      "amount": "<amount>",
      "wallet_address": "<wallet_address>"
    },
    "name": "unstake_lst"
  }
}

Input Schema

Name	Required	Description	Default
`amount`	Yes
`verify`	No
`caller_id`	No
`lst_token`	Yes
`pay_in_crank`	No
`payment_header`	No
`wallet_address`	Yes
`idempotency_key`	No
`signed_transaction`	No

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedAug 11, 2026

addedInput schema / properties / signed_transaction

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

addedInput schema / properties / verify

Added value: +{
+  "default": true,
+  "type": "boolean"
+}

First observedJul 27, 2026

TDQS

A4.6/5.0

Behavior5/5

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

The description goes well beyond annotations: it reveals non-custodial execution, that the returned transaction is unsigned and base64, that fees are charged past the free tier, and that re-trying with the same idempotency key replays the original result rather than re-uming an unknown current action. It also explains the Crank broadcast confirmation and balance-re-read behavior.

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 long but every sentence adds a meaning: purpose, units, mint selection, returning format, costing. It keeps repeated details compressed by saying 'see liquid_stake' instead of duplicating the two-phase protocol. The layout groups the optional key and the signed transaction phases into understandable chunks.

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?

Given a 9-parameter tool with an existing output schema, the description covers the main decision points and risks: route selection, base units, unsigned return step, idempotency replay, and two-phase broadcast. It delegates a part of the two-phase detail to liquid_stake and leaves one or two optional params unexplained, but those are optional and defaulted.

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

Parameters4/5

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

With 0% schema description coverage, the description must carry the load. It does: amount is 'in base unit', lst_token is clearly one of mSOL/jitoSOL/bSOL, idempotency_key behavior is fully explained, and payment_header is tied to fee context. However, wallet_address (a required parameter) and pay_in_crank/caller_id are left to inference, so it is not fully complete.

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 opens with a specific verb and resource: 'Unstake an LST back to SOL'. It also clarifies non-custodial ownership and returns an unsigned transaction, so an agent can distinguish this from related staking, swapping, and bridge tools. This is more than minimally clear.

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 implicit but unmistakable: 'Unstake an LST' tells an agent when this tool is the right one. It also gives route-specific behavior and the two-phase execution flow, but it doesn't name alternatives or use when-not-to-use language. Clear context but no explicit exclusions.

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

All Crank Protocol tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?