Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cl_alert_history

Retrieve margin call and liquidation alert history for institutional credit line accounts to review risk events, analyze LTV thresholds, and audit alerts.

Instructions

Get margin call and liquidation alert history for credit line account.

⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT

Alert Types:

  • MARGIN_CALL: Warning that LTV is approaching liquidation threshold

  • LIQUIDATION_CALL: Critical alert that liquidation is imminent/occurring

Each alert record includes:

  • alertTime: When the alert was triggered

  • alertType: MARGIN_CALL or LIQUIDATION_CALL

  • currentLTV: LTV ratio at alert time

  • initialLTV, marginCallLTV, liquidationLTV: Threshold values

  • totalBalance: Total account balance at alert time

  • loanAssets: Loan details at alert time

  • balances: Asset balances with free, locked, freeze amounts

Use this to:

  • Review past risk events

  • Understand account risk patterns

  • Audit margin call history

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

Input Schema

NameRequiredDescriptionDefault
limitNoMax records (default: 200)
endTimeNoEnd timestamp in milliseconds
alertTypeNoFilter by alert type
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.8/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 a solid job: it flags the institutional credit line agreement requirement up front, defines the two alert types and their severity semantics, and enumerates what each record contains. It omits operational traits such as pagination, ordering, and empty-result behavior, but the safety/prerequisite context is well covered.

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?

The prerequisite warning is front-loaded before any detail, and the header-plus-bullet structure makes purpose, alert types, record fields, and use cases scannable. The field enumeration earns its space because 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?

For a read-only history endpoint with no output schema, the definition supplies the return-field breakdown, the access prerequisite, and the meaning of the risk levels — enough to call it correctly. The remaining gap is behavioral: no statement of ordering, pagination, or what an empty history looks like.

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 limit, startTime, endTime, and recvWindow are already documented. The description adds real meaning only for one parameter by explaining what MARGIN_CALL and LIQUIDATION_CALL signify; it says nothing about time-range semantics (inclusive/exclusive, defaults) beyond what the schema states, so the baseline of 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?

The first line gives a specific verb and resource ("Get margin call and liquidation alert history for credit line account") and names the sub-domain (institutional credit line), so an agent knows exactly what is returned. It stops short of distinguishing itself from the very similarly named sibling binance_us_cl_liquidation_history, leaving that overlap unresolved.

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" block gives concrete scenarios (review past risk events, understand risk patterns, audit margin call history) and the warning banner establishes a hard prerequisite. However, it never says when NOT to use it or which sibling covers the adjacent liquidation-only or transfer history cases, which matters given near-duplicate sibling names.

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