Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_subaccount_summary

Retrieve the total USD value of assets across the master account and all sub-accounts, with optional filtering by sub-account email and pagination.

Instructions

Get the total USD value of assets in the master account and all 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_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number
sizeNoResults per page
emailNoFilter by specific sub-account email
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 disclosure burden and delivers little: no statement about authentication requirements, rate limits, whether the value is a live snapshot or a cached total, or what the response looks like. The presence of page and size parameters on a tool described as returning 'the total' is unexplained and actively confusing.

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 no filler or redundancy; the scope constraint lands in the first read. It is efficient but so terse that it leaves no room for the operational detail this tool needs.

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?

There is no output schema and no annotations, so the description must explain the return shape on its own, and it does not say whether the result is one number, a per-account breakdown, or paginated records. Given four parameters including paging controls, this is materially under-specified.

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 four parameters are documented and the baseline of 3 applies. The description adds nothing about how email interacts with the 'all sub-accounts' claim, nor why page/size exist for an aggregate total.

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 ('Get the total USD value of assets') plus the exact scope ('master account and all sub-accounts'), which separates it from binance_us_subaccount_assets by being an aggregate rather than a per-asset breakdown. It does not name or route away from any sibling explicitly, and it never addresses the email filter that would narrow scope below 'all sub-accounts'.

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 or when-not-to-use guidance and no named alternative; the agent must infer that this is for portfolio-wide valuation rather than per-sub-account reporting. The description also gives no hint about paginating through accounts, so an agent has no cue about its relationship to binance_us_subaccount_list.

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