Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_subaccount_list

Lists all Binance.US sub-accounts and filters results by email or enabled/disabled status, with pagination controls for reviewing account access.

Instructions

Get a list of all sub-accounts. Filter by email or status (enabled/disabled).

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

Input Schema

NameRequiredDescriptionDefault
pageNoPage number. Default: 1
emailNoFilter by sub-account email
limitNoResults per page. Default: 500
statusNoFilter by status: 'enabled' or 'disabled'
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

B3.3/5.0
Behavior2/5

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

With no annotations, "Get" only implicitly communicates a read-only, non-destructive operation; the description adds scope and filtering behavior but no authentication, rate-limit, pagination, or response details. In particular, "all sub-accounts" is not reconciled with the schema's page and limit controls, leaving whether one call returns every result unclear.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences front-load the resource and then the available filters, with no filler or unnecessary wording. The wording is highly efficient, although the unqualified "all" slightly reduces precision.

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 simple read tool with five optional, flat parameters, the core action and filters plus the fully described schema support basic invocation. However, with neither annotations nor an output schema, the definition leaves operational behavior, pagination expectations, result shape, and sibling selection guidance unaddressed.

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 baseline of 3 applies. The description repeats the email and status filters and the enabled/disabled values already documented in the schema, while adding no further meaning for page, limit, or recvWindow.

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 retrieval verb and resource—"Get a list of all sub-accounts"—and identifies email and status filtering. It does not explicitly distinguish this operation from sibling sub-account status or summary tools, so it is clear but not fully differentiating.

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?

The description implies when to choose the tool: listing sub-accounts or narrowing the list by email or enabled/disabled status. It provides no explicit exclusions, prerequisites, or alternative-tool guidance, leaving selection against similarly named siblings to inference.

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