Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_account_info

Retrieve Binance account permissions and status to validate API configuration and ensure trading, deposit, and withdrawal features are active.

Instructions

👤 账户基础信息 - 权限状态全面查看

🔍 功能说明: 获取Binance账户的基本信息和权限状态,包括账户类型、交易权限、提现权限、充值权限等核心信息。用于验证账户配置是否正确,确认各项功能可用性。

⚠️ 重要提醒: • 权限限制:某些地区或账户等级可能有特定交易限制 • 实名验证:未完成KYC认证可能影响交易和提现权限 • 安全设置:建议开启双重认证以提高账户安全性 • 定期检查:账户权限可能因合规要求发生变化

🎯 适用场景: • 新用户验证API配置和账户状态是否正常 • 程序化交易前确认账户具备所需权限 • 故障排查时检查账户状态和权限设置 • 合规检查确认账户满足交易要求

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

👤 Binance 账户信息概览

✅ 账户状态:
账户类型:SPOT(现货账户)
账户等级:VIP 1
更新时间:2024-01-15 15:30:25
余额币种:15种资产

🔐 交易权限:
现货交易:✅ 已开启
杠杆交易:✅ 已开启 (已完成风险评估)
期权交易:❌ 未开启
期货交易:✅ 已开启 (风险等级:中)

💰 资金权限:
充值功能:✅ 已开启
提现功能:✅ 已开启 (24h限额: 100 BTC)
内部转账:✅ 已开启
跨所转账:✅ 已开启

🔒 安全设置:
双重认证:✅ 已开启 (Google Authenticator)
防钓鱼码:✅ 已设置
白名单地址:✅ 已启用提现白名单
登录限制:✅ IP白名单已生效

📊 账户特征:
API使用:活跃状态
账户年龄:365天
交易活跃度:高频用户
风险等级:低风险

💡 安全建议:
账户权限正常,所有核心功能均已开启。
建议定期检查安全设置,保持最新的风控措施。
如需提高限额,请联系客服或完成更高等级认证。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It includes important reminders about regional restrictions, KYC, security settings, and potential compliance changes. The detailed output example shows exactly what the tool returns, making behavior transparent, though it does not explicitly label the operation as read-only.

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

Conciseness3/5

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

The description is well-structured with headings and sections, but it is quite lengthy due to the extensive output example and reminders. While every section contributes value, it could be tightened without losing essential information.

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 parameters and no output schema, the description fully compensates by providing a comprehensive output example and usage scenarios. It covers all necessary aspects for an agent to understand when to use the tool and what it returns.

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 the baseline is 4. The description adds no parameter details, but none are needed since the tool requires no inputs.

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 clearly states the tool retrieves Binance account basic information and permission status, specifying account type, trading/withdrawal/deposit permissions. However, it does not distinguish from the sibling tool binance_account_status, which may have overlapping functionality.

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?

Provides an '适用场景' (applicable scenarios) section listing four concrete use cases: verifying API configuration, pre-trading permission checks, troubleshooting, and compliance checks. This offers clear context but does not explicitly mention when not to use the tool or alternatives.

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