Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_stake

Stakes a supported asset on Binance.US to earn staking rewards, with optional automatic restaking.

Instructions

Stake a supported asset on Binance.US to earn staking rewards.

⚠️ IMPORTANT:

  • Staking locks your assets for a period of time

  • Check unstakingPeriod using binance_us_staking_asset_info before staking

  • Ensure you have sufficient balance before staking

  • Verify min/max staking limits for the asset

Parameters:

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

  • amount: Amount to stake

  • autoRestake: Whether to automatically restake rewards (default: true)

Response includes:

  • result: SUCCESS or failure status

  • purchaseRecordId: Record ID for the staking transaction

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_stake"
  }
}

Input Schema

NameRequiredDescriptionDefault
amountYesAmount to stake
autoRestakeNoAutomatically restake rewards (default: true)
stakingAssetYesAsset symbol to stake (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.9/5.0
Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does well: it states that assets are locked for a period, that balance and min/max limits must be checked first, that autoRestake defaults to true, and what the response returns (result, purchaseRecordId). It omits permission requirements, rate limits, and whether a partial/failed stake is possible, which keeps it from a 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?

The description is front-loaded with purpose, then a bolded warning block, then compact parameter and response lists — easy to scan. The parameter section duplicates the schema verbatim, which is minor waste, but the overall structure is clean and nothing critical is buried.

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 3-parameter mutation with no output schema and no annotations, the description covers the key behavioral risks (locking period, prerequisites, limits) and describes the return fields itself. What remains missing is narrower: permission requirements, failure modes, and actual limit values, which are reasonably deferred to binance_us_staking_asset_info.

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 coverage is 100%, so all three parameters are already documented in the schema. The description's parameter list largely restates what the schema says (amount, asset examples, autoRestake default) with no added syntax, precision, or edge-case guidance, 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 and resource: 'Stake a supported asset on Binance.US to earn staking rewards,' which lets an agent distinguish this from the sibling binance_us_staking_unstake without opening either schema. It stops just short of 5 because it never explicitly names the unstake operation as the inverse action an agent might confuse it with.

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?

It gives concrete preconditions: check unstakingPeriod via binance_us_staking_asset_info, ensure sufficient balance, and verify min/max staking limits — each naming a specific tool or check an agent must perform first. There is no explicit 'do not use this when...' exclusion, but the lock warning effectively cautions against staking assets the user may need liquid.

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