Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_balance

Retrieve current staking balances and position details for one or all staked assets on Binance.US, including amounts, APR, APY, and auto-restake status.

Instructions

Get current staking balance for assets on Binance.US.

Returns your current staking positions and their details.

Response includes for each staked asset:

  • asset: The staked asset symbol

  • stakingAmount: Total amount currently staked

  • rewardAsset: Asset received as rewards

  • apr: Current APR for the asset

  • apy: Current APY (with compounding)

  • autoRestake: Whether auto-restaking is enabled

If no asset is specified, returns balances for all staked 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_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetNoStaked asset symbol. If empty, returns all assets with balances

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.6/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 well: it enumerates exactly what each returned entry contains (asset, stakingAmount, rewardAsset, apr, apy, autoRestake) and clarifies the empty-parameter behavior. It leaves out auth requirements, rate limits, and error/pagination behavior, which keeps it short of a 5 for an unannotated tool.

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 definition is front-loaded with the purpose, then uses a compact bullet list for return fields, and ends with the default scope. Most sentences earn their place; the apr/apy parentheticals are slight padding but aid interpretation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Since there is no output schema, the field enumeration is genuinely valuable and covers the return shape. However, for a financial read tool with no annotations, it omits prerequisites such as authentication and whether data is account-scoped, leaving a meaningful gap.

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%, and the single optional 'asset' parameter is already documented in the schema as a staked asset symbol with empty meaning all assets. The description's closing sentence largely restates that, adding little new semantic detail such as symbol format or case sensitivity.

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 ('Get current staking balance for assets on Binance.US'), making it immediately clear this is a read of staking positions. It does not explicitly distinguish itself from close siblings like binance_us_staking_rewards, binance_us_staking_history, or binance_us_staking_asset_info, so the agent must infer the boundary.

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 is implied rather than stated: the tool returns 'current staking positions,' which suggests it is for reading holdings rather than staking/unstaking or checking history. There is no explicit when-to-use, when-not-to-use, or named alternative among the many staking siblings.

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