Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_portfolio_account

Get unified Portfolio Margin account details: total margin, available balance, unrealized PnL, asset distribution, and margin usage. Monitor cross-asset risk across spot and futures.

Instructions

🏦 统一账户总览 - Portfolio Margin 全资产管理

🔍 功能说明: 获取统一账户(Portfolio Margin)的完整信息,包括总保证金、可用余额、未实现盈亏、各币种资产分布、保证金使用率等核心数据。提供跨现货和合约的全局资产视角。

⚠️ 重要提醒: • 保证金模式:统一账户支持跨品种保证金共享,风险更集中 • 强平风险:保证金不足时可能触发全账户强制平仓 • 计算复杂:涉及现货、合约、期权等多种资产的综合评估 • 实时变动:盈亏和保证金状态随市价实时变动

🎯 适用场景: • 专业交易者查看整体资产配置和风险状况 • Portfolio Margin用户监控保证金使用率 • 风控系统评估账户整体风险敞口 • 资产配置优化和再平衡决策

🏛️ 输出示例: 查询成功后将返回:

🏦 统一账户(Portfolio Margin)资产总览

⚖️ 保证金概况:
总保证金余额:125,847.50 USDT
可用余额:58,234.75 USDT
最大可提取:45,123.25 USDT
保证金使用率:53.7%(中等风险)

📊 保证金构成:
钱包余额:130,250.00 USDT
未实现盈亏:-4,402.50 USDT
持仓保证金:45,678.25 USDT
订单保证金:21,934.50 USDT

💰 资产分布:

🟡 USDT(主要计价资产)
钱包余额:85,450.50 USDT
未实现盈亏:-2,150.75 USDT
保证金余额:83,299.75 USDT
维持保证金:12,458.50 USDT
初始保证金:18,925.75 USDT

₿ BTC(比特币)
钱包余额:0.75000000 BTC
未实现盈亏:-0.02450000 BTC(-1,058.50 USDT)
保证金余额:0.72550000 BTC
当前价值:31,289.75 USDT

🔷 ETH(以太坊)
钱包余额:5.25000000 ETH
未实现盈亏:+0.15750000 ETH(+393.75 USDT)
保证金余额:5.40750000 ETH
当前价值:13,518.75 USDT

⚡ 风险指标:
保证金比例:186.4%(安全)
维持保证金率:24.8%
强平风险:低风险
资产质量:优质资产为主

📈 持仓影响:
合约持仓价值:67,892.50 USDT
现货持仓价值:58,955.00 USDT
总敞口:126,847.50 USDT
敞口占比:100.8%(满仓状态)

💡 风险建议:
当前保证金使用率适中,但接近高位。
建议保留更多可用保证金以应对市场波动。
未实现亏损较大,需关注持仓风险。
考虑适当减少敞口或增加保证金资金。

⚠️ 特别提醒:
统一账户风险共享,任一品种大幅波动都可能影响全账户。
建议设置合理的风险管理策略和止损机制。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

No annotations are provided, so the description fully carries the burden. It explicitly warns about margin sharing risks, liquidation risk, calculation complexity, and real-time fluctuations. The output example also reveals the response format and fields.

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?

The description is long but well-structured with emoji headers, sections for features, warnings, scenarios, and an output example. It's front-loaded with a summary sentence and each section has purpose, though it could be trimmed slightly for brevity.

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

Completeness5/5

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

With no annotations and no output schema, the description provides a complete picture: functionality, risk implications, use cases, and an example output. This fully compensates for missing structured metadata.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so there's no parameter to explain. The description compensates by detailing the output data structure, but the baseline for a zero-param tool is 4; it doesn't add extra param-level semantics beyond that.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states '获取统一账户(Portfolio Margin)的完整信息' (get complete info of unified account), which clearly identifies a specific verb and resource. It distinguishes from siblings like binance_account_info by focusing on Portfolio Margin unified account and cross-spot/futures asset view.

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

Usage Guidelines4/5

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

The '适用场景' section lists concrete use cases such as professional traders viewing asset allocation, monitoring margin usage, and risk control. It doesn't explicitly mention alternatives or exclusion criteria, but the context is clear and domain-specific.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kydlikebtc/binance-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server