Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_custodial_settlement_history

Retrieve settlement history from a custodial sub-account to a custodial partner, including status, amounts, and timestamps; filter results by rail, asset, settlement ID, or time range.

Instructions

Get history of settlements from custodial sub-account to custodial partner.

⚠️ REQUIRES CUSTODIAL SOLUTION API KEY

Returns settlement history with status, amounts, and timestamps.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number (default: 1)
railYesCustodial partner identifier (all uppercase)
assetNoFilter by asset (e.g., BTC)
limitNoResults per page (default: 20, max: 100)
endTimeNoEnd time in milliseconds
startTimeNoStart time in milliseconds
settlementIdNoFilter by specific settlement ID
clientOrderIdNoFilter by your reference ID

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

B3.2/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 burden. It does disclose the auth prerequisite (custodial solution API key) and the shape of the return (status, amounts, timestamps), but says nothing about read-only semantics, rate limits, pagination behavior, or empty-result handling.

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?

Two short blocks with the auth warning front-loaded and the return summary second; no filler. Slightly more could be trimmed (the warning could be one clause), but nothing 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 an eight-parameter read tool with no annotations and no output schema, the definition covers auth and return fields and leans on a fully documented schema. It still omits read-only/safety framing and any differentiation from the duplicate-looking sibling, which an agent would need to choose correctly.

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 all eight parameters including the required rail identifier and the time-range filters are already documented. The description adds no parameter meaning beyond the schema, 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?

States a specific verb and resource plus the direction of flow: settlements from custodial sub-account to custodial partner. That is more precise than a bare name restatement, though it never distinguishes itself from the near-identically named sibling binance_us_cust_settlement_history or from binance_us_custodial_settlement.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no when-to-use framing beyond the implicit 'this is a history lookup'. No alternatives are named, no exclusions are given, and the agent is left to infer how this differs from the several settlement/transfer history siblings.

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