Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_rewards

Retrieve staking rewards history for assets on Binance.US, with optional asset and time filters. Returns amounts, USD values, timestamps, and auto-restake status.

Instructions

Get staking rewards history for assets on Binance.US.

Returns a history of staking rewards earned over time.

Response includes:

  • total: Total number of reward records

  • data: Array of reward records

Each reward record contains:

  • asset: The reward asset

  • amount: Reward amount

  • usdValue: USD value at time of reward

  • time: Reward timestamp

  • tranId: Transaction ID

  • autoRestaked: Whether the reward was automatically restaked

If no asset is specified, returns rewards 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_rewards"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage/batch number
assetNoStaked asset. If empty, returns all assets with rewards
limitNoRecords per batch (default: 500)
endTimeNoEnd timestamp in milliseconds
startTimeNoStart timestamp in milliseconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does well on return shape, enumerating total, data, and each record field, but it says nothing about pagination behavior despite page and limit parameters, nor about rate limits or authentication requirements.

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 purpose and then uses a clean bulleted structure for the response fields, which is easy to scan. The second sentence ('Returns a history of staking rewards earned over time') largely restates the first and could be dropped.

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?

With no output schema and no annotations, the description appropriately compensates by documenting the response envelope and record fields in detail. The main remaining gap is pagination guidance for the page and limit parameters, which matters for a history endpoint.

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 baseline is 3. The description adds one useful clarification, that omitting asset returns rewards for all staked assets, but says nothing about page, limit, startTime, or endTime semantics beyond what the schema already states.

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 staking rewards history for assets on Binance.US,' which is unambiguous about what is retrieved. It does not, however, distinguish itself from the sibling 'binance_us_staking_history', which an agent could easily confuse with this tool.

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 only implied by the phrase 'history of staking rewards earned over time'; there is no explicit when-to-use or when-not-to-use guidance. No alternative tool is named, so the agent must infer that this is the rewards-specific counterpart to the general staking history tool.

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