Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_settlement

Settles assets from a Binance.US custodial sub-account to your custody partner's vault by withdrawing a specified asset amount through a chosen rail.

Instructions

Request settlement of assets from custodial sub-account to custodial partner.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY ⚠️ This sends funds to your custodial partner!

This settles (withdraws) assets from your Binance.US custodial sub-account to your custody partner's vault.

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": {
      "rail": "<rail>",
      "asset": "<asset>",
      "amount": "<amount>"
    },
    "name": "binance_us_custodial_settlement"
  }
}

Input Schema

NameRequiredDescriptionDefault
railYesCustodial partner identifier (all uppercase)
assetYesAsset to settle (e.g., BTC, ETH)
amountYesAmount to settle
clientOrderIdNoYour reference ID (auto-generated if not provided)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  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 supplied, the description carries the full burden and does disclose the two most important traits: a specific credential is required and the call actually moves funds out to an external partner. It does not say whether the settlement is reversible, how long it takes to complete, or whether fees/minimums apply, which are material for a fund-moving operation.

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?

The core action and the two warnings are front-loaded, and the closing sentence clarifies the withdrawal semantics. Minor redundancy between "Request settlement" and "This settles (withdraws) assets", but no sentence is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a destructive, unannotated, no-output-schema mutation tool, the description covers auth and fund movement but leaves the agent without the response shape, confirmation/status semantics, or timing expectations. Adequate to avoid misuse, but not complete for a high-risk financial operation.

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 rail, asset, amount and clientOrderId are already documented in the schema, including the uppercase constraint on rail and the auto-generation behavior of clientOrderId. The description adds no format, constraint, or example detail beyond that, so the baseline 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?

States a specific verb and resource ("Request settlement of assets") plus the direction of movement (custodial sub-account → custodial partner's vault), which distinguishes it from the history/settings siblings. It does not explicitly contrast with the fund-moving siblings like binance_us_custodial_wallet_transfer or binance_us_custodial_custodian_transfer, so an agent must infer that distinction from the word "settlement".

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 clear context for when to invoke it: settling assets out of a custodial sub-account to the custody partner. Prerequisites are stated (requires a Custodial Solution API key). There is no explicit "when not to use" or named alternative for moving funds between wallets versus settling to the partner.

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