Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cl_transfer

Transfers assets into or out of a Binance.US institutional credit line account to add collateral or withdraw funds while accounting for LTV impact.

Instructions

Execute a transfer in or out of the credit line account.

⚠️ REQUIRES INSTITUTIONAL CREDIT LINE AGREEMENT

⚠️ WARNING: Transfers affect your LTV ratio!

  • TRANSFER_OUT increases LTV (more risk)

  • TRANSFER_IN decreases LTV (less risk)

Before transferring out, ensure:

  1. Your LTV won't exceed marginCallLTV after transfer

  2. You have sufficient availableAmountToTransferOut

  3. You understand the impact on your credit position

Transfer Types:

  • TRANSFER_IN: Add collateral to credit line account

  • TRANSFER_OUT: Withdraw from credit line account

Response includes:

  • transferId: Unique transfer identifier

  • status: SUCCESS, PENDING, or FAILED

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "transferType": "<transferType>",
      "transferAssetType": "<transferAssetType>",
      "quantity": "<quantity>"
    },
    "name": "binance_us_cl_transfer"
  }
}

Input Schema

NameRequiredDescriptionDefault
quantityYesAmount to transfer
recvWindowNoRequest validity window (max: 60000)
transferTypeYesDirection: TRANSFER_IN (deposit) or TRANSFER_OUT (withdraw)
transferAssetTypeYesAsset to transfer (e.g., BTC, USD)

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.1/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 well: it discloses the institutional agreement requirement, the risk consequence of each direction (LTV up/down), pre-transfer verification steps, and the response shape (transferId, status values SUCCESS/PENDING/FAILED). It omits idempotency/retry behavior, rate limits, and how PENDING or FAILED statuses should be handled.

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 action, then warnings, a numbered precondition checklist, transfer types, and response fields — all useful and scannable. Slight redundancy between the warning bullets and the numbered checklist keeps it from being maximally tight.

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 mutation tool with no annotations and no output schema, the description covers prerequisites, risk, valid directions, and return fields, which is close to sufficient. What's missing is failure-mode guidance (what to do on PENDING/FAILED) and any note on permissions or idempotency.

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 description coverage is 100%, so the baseline is 3; the schema already documents quantity, transferType enum, transferAssetType, and recvWindow. The description adds directional risk semantics ('TRANSFER_OUT increases LTV') beyond the enum's own description, but says nothing extra about recvWindow or asset-type formatting.

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?

States a specific verb ('Execute a transfer') plus the precise resource scope ('in or out of the credit line account'), which cleanly separates it from the many sibling transfer tools (cust_transfer, subaccount_transfer, custodial_wallet_transfer) that move funds elsewhere. An agent can identify the correct tool from the first sentence alone.

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?

Gives explicit preconditions for TRANSFER_OUT (LTV must stay below marginCallLTV, sufficient availableAmountToTransferOut) and explains what each direction means. It does not name any sibling alternative or say when a different transfer tool should be used instead, so it stops just short of full routing guidance.

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