Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_unstake

Unstake a previously staked asset on Binance.US by providing the asset symbol and amount; rewards stop once unstaking begins and early penalties may apply.

Instructions

Unstake a previously staked asset on Binance.US.

⚠️ IMPORTANT:

  • Unstaking may take time (check unstakingPeriod in asset info)

  • You will stop earning rewards once unstaking begins

  • Some assets may have early unstaking penalties

Parameters:

  • stakingAsset: The asset to unstake (e.g., BNB, ETH)

  • amount: Amount to unstake

Response includes:

  • result: SUCCESS or failure status

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": {
      "stakingAsset": "<stakingAsset>",
      "amount": "<amount>"
    },
    "name": "binance_us_staking_unstake"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to unstake
stakingAssetYesAsset symbol to unstake (e.g., BNB, ETH)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does reasonably well: it discloses that unstaking is asynchronous (unstakingPeriod), that reward accrual stops immediately, and that early-exit penalties may apply — all traits an agent would otherwise not know. It omits whether the request can be cancelled, whether it is idempotent, and any auth/account requirements, which caps it below 5.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the action, then a clearly delimited warning block and response note; easy to scan. The dedicated 'Parameters' section duplicates the schema verbatim and could be cut without losing information, which is the only real waste.

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 2-parameter mutation with no output schema, the description covers the important bases: timing behavior, reward loss, penalty risk, and a rough shape of the response (SUCCESS or failure). What remains thin is what the agent should do after calling (e.g., poll staking_asset_info for unstakingPeriod status) and failure modes such as insufficient staked balance.

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 schema already documents both parameters and the description's parameter block merely restates them with the same examples (BNB, ETH). No additional meaning is added — nothing about partial vs full unstake, precision, or minimums — 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 opens with a specific verb+resource ('Unstake a previously staked asset on Binance.US'), which is enough to separate it from the obvious inverse sibling binance_us_staking_stake without opening either schema. It stops short of explicitly naming that sibling or any other alternative, which keeps it at 4 rather than 5.

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?

Usage context is implied by 'previously staked asset' and by the warnings that rewards stop and penalties may apply, which tells the agent this is a terminating action. However, there is no explicit prerequisite (must hold a staked balance, minimum amount, whether partial unstaking is allowed) and no named alternative such as asset_info for checking eligibility beforehand.

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