Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_asset_info

Retrieve staking details for Binance.US assets, including APR, APY, staking limits, unstaking period, and auto-restake, for one asset or all supported assets.

Instructions

Get staking information for supported assets on Binance.US.

Returns details about staking options including APR, APY, and staking limits.

Response includes for each asset:

  • stakingAsset: Asset being staked (e.g., BNB, ETH)

  • rewardAsset: Asset received as staking reward

  • apr: Annual Percentage Rate (without compounding)

  • apy: Annual Percentage Yield (with compounding/restaking)

  • unstakingPeriod: Time to unstake in hours (e.g., 168 = 7 days)

  • minStakingLimit: Minimum amount allowed for staking

  • maxStakingLimit: Maximum amount allowed for staking

  • autoRestake: Whether rewards are automatically restaked

If no asset is specified, returns information for all staking assets.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "binance_us_staking_asset_info"
  }
}

Input Schema

NameRequiredDescriptionDefault
stakingAssetNoAsset symbol (e.g., BNB, ETH). If empty, returns all staking assets

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

B3.2/5.0
Behavior3/5

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

With no annotations provided, the description carries the full behavioral burden. It discloses that this is a retrieval operation, the optional-asset fallback, and the returned fields, but it does not mention authentication requirements, rate limits, error behavior, or whether the endpoint is public or account-specific.

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 the core purpose and then uses a structured field list to explain return values. The field list is somewhat long, but it earns its place because no output schema is provided and the response fields carry meaningful domain semantics.

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 optional-parameter retrieval tool with no output schema, the description covers the purpose, fallback behavior, and all returned field meanings. The remaining gaps are mainly usage routing against sibling tools and missing operational details such as auth or rate limits.

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 single stakingAsset parameter is already documented by the schema. The description repeats the empty-value fallback but adds no new syntax or constraints beyond what the schema provides.

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 states a specific verb and resource: getting staking information for supported assets on Binance.US, including APR, APY, and limits. It is clearly a retrieval tool for staking options, but it does not explicitly name or differentiate itself from sibling tools such as staking_balance, staking_history, staking_rewards, stake, or unstake.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies retrieval of staking asset information and explains the no-parameter fallback, but it provides no explicit when-to-use guidance versus alternatives. It does not say when to choose this tool over staking_balance, staking_history, staking_rewards, staking_stake, or staking_unstake.

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