Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cl_transfer_history

Retrieves transfer history for a Binance.US institutional credit line account, including deposits, withdrawals, assets, amounts, statuses, and timestamps for tracking collateral and reconciling activity.

Instructions

Get transfer history for credit line account.

⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT

Transfer Types:

  • TRANSFER_IN: Deposits into credit line account

  • TRANSFER_OUT: Withdrawals from credit line account

Each transfer record includes:

  • transferId: Unique transfer identifier

  • transferType: TRANSFER_IN or TRANSFER_OUT

  • asset: Transferred asset symbol

  • amount: Transfer amount

  • status: Transfer status (SUCCESS, PENDING, FAILED)

  • transferTime: When the transfer occurred

Use this to:

  • Track collateral movements

  • Audit deposit/withdrawal history

  • Reconcile account activity

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

Input Schema

NameRequiredDescriptionDefault
assetNoFilter by asset (e.g., BTC, USD)
limitNoMax records (default: 20, max: 100)
endTimeNoEnd timestamp in milliseconds
startTimeNoStart timestamp in milliseconds
recvWindowNoRequest validity window (max: 60000)
transferTypeNoFilter by transfer direction

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the institutional agreement gate and enumerates the record shape (transferId, transferType, asset, amount, status, transferTime) including status values. It omits behavioral details such as query time-window limits, rate limits, or pagination semantics.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the purpose and the warning, then cleanly sectioned into transfer types and record fields. Every block earns its place, and the field list compensates for the absent output schema rather than being filler.

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 six-parameter read tool with no output schema and no annotations, the description supplies the missing return-value documentation and the eligibility gate. It could be stronger by noting any historical date-range restriction or result-limit behavior an agent would hit in practice.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning the schema does not: it defines TRANSFER_IN as a deposit into the credit line account and TRANSFER_OUT as a withdrawal, resolving the direction semantics of the enum filter rather than just restating it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Get transfer history") and immediately scopes it to the credit line account, which is enough to distinguish it from the sibling subaccount/custodial/cust transfer history tools without opening any schema.

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 states a hard prerequisite ("REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT") that gates whether an agent should call it at all, and lists intended uses (track collateral, audit deposits/withdrawals, reconcile activity). It stops short of naming when to switch to a sibling transfer-history tool instead.

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