Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_subaccount_transfer_history

Retrieve transfer history between master and sub-accounts, with filters for email, time range, and pagination.

Instructions

Get transfer history between master and sub-accounts.

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number. Each page contains up to 500 records
emailNoSub-account email to filter by
limitNoResults per page. Default: 500
endTimeNoEnd time in milliseconds
startTimeNoStart time in milliseconds
recvWindowNoThe value cannot be greater than 60000

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

C2.9/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full burden of behavioral disclosure. It implies a read-only history query but says nothing about pagination limits (the schema hints at 500 per page), default time-range behavior when startTime/endTime are omitted, rate limits, or data retention — all material for a historical query tool.

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?

A single front-loaded sentence with zero filler; the action and scope land immediately. Its brevity is a symptom of under-specification rather than verbosity, so it scores well here but not perfectly.

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

Completeness2/5

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

For a six-parameter financial history tool with no annotations and no output schema, the description is too thin. It never states what a record contains, whether results are newest-first, or what happens with absent time filters — gaps an agent needs filled before calling 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% and all six parameters are documented with units and defaults, so the schema does the heavy lifting. The description adds no extra meaning such as whether email must belong to an existing sub-account or how startTime/endTime interact with page.

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 gives a specific verb ('Get') and resource ('transfer history between master and sub-accounts'), so the core action is unambiguous. It fails to distinguish itself from siblings such as binance_us_subaccount_transfer (the write-side counterpart) or binance_us_cust_transfer_history, so an agent cannot route between them on this text alone.

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?

The description offers no when-to-use guidance, no exclusions, and no mention of prerequisites such as needing a sub-account email or a bounded time window. The agent is left to infer that this is the read-side counterpart of the transfer tool.

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