Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_staking_history

Fetch staking and unstaking transaction history for Binance.US assets, with optional asset and time filters, to review amounts, timestamps, and statuses.

Instructions

Get staking transaction history for assets on Binance.US.

Returns a history of staking and unstaking transactions.

Response includes for each transaction:

  • asset: The asset involved

  • amount: Transaction amount

  • type: Transaction type (staked, unstaked, etc.)

  • initiatedTime: Transaction initiation timestamp

  • status: Transaction status (SUCCESS, PENDING, etc.)

If no asset is specified, returns history for all 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_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
assetNoAsset symbol. If empty, returns all assets with history
limitNoRecords per page (default: 500, max: 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

B3.2/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 burden. It discloses the return shape and status values (SUCCESS, PENDING), which is genuinely useful, but omits rate limits, auth requirements, and pagination traversal behavior for a 500-record-capped endpoint.

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 purpose sentence, then a compact bulleted return-field list. Every line carries information, though the bulleted field enumeration is the bulk of the text and borders on verbose for a read tool.

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, enumerating the returned fields is the right compensating move and makes the definition sufficient to interpret results. The remaining gap is that an agent gets no hint that results are paged (500 max per page) and may need to iterate.

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 five parameters are already documented, including defaults and the max-500 limit. The description's 'all assets when no asset specified' restates the schema's asset description rather than adding new meaning. 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?

States a specific verb and resource ('Get staking transaction history') and clarifies scope as both staking and unstaking transactions, which separates it from action-oriented siblings like staking_stake/staking_unstake. It does not explicitly distinguish itself from staking_rewards or staking_balance, so the differentiation is inferable rather than stated.

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 only guidance is a parameter-behavior note ('If no asset is specified, returns history for all assets'). There is no statement of when to prefer this over staking_rewards, staking_balance, or staking_asset_info, and no exclusions or prerequisites.

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