Skip to main content
Glama
Binance.US MCP Server

Binance.US MCP Server

by nirholas

binance_us_subaccount_status

Retrieve sub-account status details, including activation state and enabled features, to verify account readiness and permissions.

Instructions

Get status list of sub-accounts including activation status and enabled features.

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

Input Schema

NameRequiredDescriptionDefault
emailNoSub-account email to check status for
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.2/5.0
Behavior3/5

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

With no annotations present, the description must carry the full behavioral burden. It augments the name by disclosing what the response contains ('activation status and enabled features') and implies a read-only operation via 'Get', but it does not mention authentication requirements, rate-limit weight, or whether omitting email returns all sub-accounts.

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. It is efficient, though its brevity leaves the reader with little beyond the resource name and the returned fields.

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?

Without annotations or an output schema, the description should be more self-sufficient. It identifies the returned data at a high level but leaves open the behavior of the optional email parameter, the response shape, and the auth requirements of a private account endpoint.

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 both parameters (email and recvWindow) are already documented in the schema. The description does not clarify the important ambiguity that email is optional and what happens when it is omitted, so it adds no meaning beyond the schema.

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 ('status list of sub-accounts') and names the fields returned: activation status and enabled features. It is clearly a read of sub-account status, though it does not explicitly differentiate itself from siblings like binance_us_subaccount_list or binance_us_subaccount_summary.

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 guidance on when to use this instead of the adjacent sub-account tools (list, summary, assets), no prerequisites, and no exclusions. An agent must infer the context from the tool name alone.

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