Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_cust_settlement_history

Retrieve historical settlement records for a custodial partner, including status, trigger time, settlement ID, and settled assets. Requires a custodial solution API key.

Instructions

Get historical settlement records for custodial solution.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Shows past automatic settlements to custodial partner.

Response includes:

  • records: Array of settlement records

  • total: Total number of settlements

Each record contains:

  • status: PROCESS, SUCCESS, or FAILURE

  • triggerTime: When settlement was triggered

  • settlementId: Unique settlement identifier

  • settlementAssets: Array of assets settled with amounts and addresses

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>"
    },
    "name": "binance_us_cust_settlement_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
railYesCustodial partner name (e.g., ANCHORAGE, BITGO). Must be uppercase.
limitNoMax records (default: 5, max: 100)
endTimeNoEnd timestamp
startTimeNoStart timestamp

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / page / maximum
      Added value: +9007199254740991
  2. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It does disclose the non-obvious auth requirement (custodial solution API key) and enumerates response fields, which is real added value, but it says nothing about read-only nature, rate limits, or pagination behavior beyond what the schema already defines.

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 credential warning is front-loaded and the response shape is broken into scannable bullets with no filler. The record-field expansion is slightly long for a read-history tool, but each line conveys genuinely useful structure.

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?

With no output schema and no annotations, the description compensates well by documenting the response envelope and record fields and by flagging the credential requirement. The remaining gap is that it does not clarify pagination/total semantics or how this differs from the closely named sibling settlement history tool.

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, page, limit, startTime, and endTime are already documented in the input schema. The description adds no extra meaning about the required rail value format or how start/end timestamps interact, leaving it at the baseline for fully documented parameters.

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 uses a specific verb+resource ('Get historical settlement records for custodial solution') and adds scope detail ('past automatic settlements to custodial partner'), which is clear. It does not, however, distinguish itself from near-identical siblings such as binance_us_custodial_settlement_history, so an agent still has to infer which one applies.

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?

Usage context is implied ('past automatic settlements') and the credential prerequisite is stated loudly, which helps qualification. There is no explicit when-to-use vs. when-not guidance and no routing to the alternative settlement history sibling, so the agent must reason about selection itself.

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