Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_account_status

Diagnose Binance API connectivity, time sync, and network mode to resolve trading problems and verify system health.

Instructions

🔧 系统连接诊断 - API状态和网络环境检查

🔍 功能说明: 检查API连接状态、服务器时间同步、账户网络模式(主网/测试网)等技术信息。用于诊断连接问题、验证配置正确性,确保交易系统正常运行。

⚠️ 重要提醒: • 连接异常:可能导致交易失败、数据延迟或系统错误 • 时间偏差:超过1000ms会影响API调用和订单执行 • 网络模式:确认是否在正确的网络环境(主网/测试网) • 定期检查:建议程序化交易系统定期进行状态检查

🎯 适用场景: • 系统启动时验证连接和配置状态 • 交易异常时排查网络和API问题 • 定期健康检查确保系统稳定运行 • 新环境部署时的配置验证

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

🔧 系统连接状态诊断报告

✅ 连接状态:
API连接:✅ 连接正常
响应速度:✅ 快速 (< 50ms)
网络稳定性:✅ 稳定
数据传输:✅ 正常

⏰ 时间同步:
服务器时间:2024-01-15 15:30:25.847 UTC
本地时间:2024-01-15 15:30:25.923 UTC
时间偏差:-76毫秒
同步状态:✅ 优秀 (偏差 < 100ms)

🌐 网络环境:
运行模式:🟢 主网 (生产环境)
API端点:api.binance.com
数据中心:新加坡
延迟等级:极低延迟

🔐 账户配置:
API密钥:✅ 有效
权限设置:✅ 正常 (现货+合约)
IP限制:✅ 已配置白名单
安全等级:✅ 高安全

📊 性能指标:
连接池状态:良好
请求频率:正常范围内
错误率:0.00%
成功率:100.00%

💡 系统状态:
所有系统组件运行正常,无需人工干预。
网络连接稳定,API响应迅速。
时间同步精确,不会影响交易执行。
安全配置完整,账户权限正常。

🔧 维护建议:
当前系统状态优秀,建议保持现有配置。
定期监控网络状态和API响应时间。
如出现连接异常,请检查网络和防火墙设置。

⚠️ 故障排除参考:
• 连接失败:检查API密钥和网络设置
• 时间偏差过大:校准系统时间或配置NTP
• 权限错误:确认API密钥权限设置
• 响应缓慢:检查网络连接和服务器负载

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It goes beyond a simple status check by explaining what is checked (connection, time sync, network mode, account config), the implications of issues (time deviation >1000ms affects calls), and provides a detailed output example. It also includes maintenance suggestions and fault-troubleshooting references, giving a complete picture of the tool's behavior.

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

Conciseness2/5

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

The description is excessively verbose, with emoji-heavy sections, a full example output report, and redundant advisory text (e.g., maintenance advice). While it is structured with headings, it contains far more detail than needed for a tool with no parameters and a straightforward purpose. Many sentences do not earn their place.

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?

Given the tool has no output schema and no annotations, the description fully compensates by explaining the return value in depth through an extensive output example. It covers the purpose, usage scenarios, interpretation of results, and troubleshooting, making it complete enough for an agent to select and invoke the tool correctly.

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 tool has zero parameters and the schema coverage is 100%, so the baseline is 4. The description correctly implies no inputs are needed and instead focuses on the output report, which adds value by explaining what the user will receive.

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 clearly states the tool checks API connection status, server time synchronization, and network mode (mainnet/testnet), positioning it as a diagnostic tool. This distinguishes it from sibling tools like binance_portfolio_account (balances) or binance_server_time (just time), by focusing on technical health.

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 description provides clear usage scenarios (system startup, troubleshooting, regular health checks, new environment deployment) and even includes troubleshooting steps for common issues. It does not explicitly mention alternative tools or when not to use this one, but the context is sufficiently clear.

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