Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cl_liquidation_history

Retrieve past liquidation events for an institutional credit line account to review liquidated assets, LTV levels, fees, and audit risk management effectiveness.

Instructions

Get liquidation history for credit line account.

⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT

Liquidations occur when LTV exceeds liquidationLTV threshold. This endpoint shows historical liquidation events.

Each liquidation record may include:

  • Liquidated assets and amounts

  • Liquidation timestamp

  • LTV at time of liquidation

  • Fees charged

Use this to:

  • Review past liquidation events

  • Understand liquidation patterns

  • Audit risk management effectiveness

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records (default: 20, max: 100)
endTimeNoEnd timestamp in milliseconds
startTimeNoStart timestamp in milliseconds
recvWindowNoRequest validity window (max: 60000)

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

A3.7/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: it discloses the credit-line eligibility gate, explains the liquidation trigger condition (LTV exceeding liquidationLTV), and enumerates the record contents. It does not cover pagination, time-window defaults, or failure behavior when no agreement exists.

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 identity statement, then the blocking requirement, then semantics, then record fields and uses. Bullets are well organized; the return-field list is slightly long but justified given there is no output schema.

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?

No output schema exists, so listing the record fields it may return is genuinely additive. Coverage of the domain concept, eligibility requirement, and payload shape makes this sufficient, with only pagination and error semantics left out.

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 the four parameters (limit, startTime, endTime, recvWindow) are already fully documented with defaults and bounds. The description adds no parameter-level meaning beyond the schema, which is the correct baseline.

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 liquidation history for credit line account') and defines liquidation via the LTV-vs-liquidationLTV threshold, which is enough to distinguish it from the alert/transfer history siblings. It could be a 5 with an explicit contrast, but the resource is self-evidently distinct.

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?

The 'Use this to' bullets describe purposes rather than selection criteria against alternatives, and no sibling or fallback is named. The 'REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT' warning is a useful eligibility precondition, which lifts it above bare implied usage.

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