Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cl_account

Retrieves credit line account details for institutional users with approved facilities, including LTV ratios, interest, permissions, loan data, and balances.

Instructions

Get comprehensive credit line account information.

⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT This API is only available to institutional users with approved credit facilities.

Response includes:

  • clAccountId: Credit line account ID

  • masterAccountId: Associated master account ID

  • notificationMailAddr: Email for notifications

LTV (Loan-to-Value) Ratios:

  • currentLTV: Current loan-to-value ratio

  • initialLTV: Initial LTV threshold

  • marginCallLTV: LTV that triggers margin call

  • liquidationLTV: LTV that triggers liquidation

Interest & Fees:

  • interestRate: Annual interest rate on loans

  • liquidationFeeRate: Fee charged on liquidation

Contract Details:

  • contractStartTime/contractEndTime: Credit facility dates

  • isActive: Whether credit line is active

Permissions:

  • canTrade: Trading permission

  • canTransferIn/canTransferOut: Transfer permissions

Loan Information:

  • loanAssets: Array of loaned assets with quantities

  • requiredDepositAmount: Additional collateral needed

  • availableAmountToTransferOut: Funds available to withdraw

Balances:

  • balances: Array of asset balances (free, locked)

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

Input Schema

NameRequiredDescriptionDefault
recvWindowNoRequest validity window in ms (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.9/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full burden and does disclose the key behavioral fact: the call only succeeds for institutional users with approved credit facilities, an auth precondition an agent cannot infer from the schema. It does not state that the operation is read-only, nor any rate-limit or weight behavior.

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?

Purpose and the institutional warning are front-loaded before the field inventory, and the grouped headers (LTV, Interest & Fees, Permissions, etc.) make the long tail skimmable. The response-field catalog is long but earns its place because there is no output schema; minor redundancy remains in the one-line-per-field format.

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 single-parameter read tool with no annotations and no output schema, the definition covers the two things an agent needs: the access precondition and a field-by-field map of the return payload. Only the read-only nature and any weight/rate-limit context are missing.

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?

There is a single optional parameter (recvWindow) and the schema already documents it at 100% coverage including units and max. The description adds nothing about it, so the schema does all the work and 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 description opens with a specific verb+resource: "Get comprehensive credit line account information." The credit-line framing plus the institutional-only warning implicitly separates it from the general account tools (binance_us_account_info, binance_us_cust_balance), though it never names a sibling to redirect to.

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?

The bolded "REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT" line gives a hard eligibility gate that tells an agent whether this tool applies at all, which is stronger than most usage guidance. It stops short of naming alternatives or stating what to do when the user has no credit facility.

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