Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_futures_klines

Fetch perpetual futures candlestick data based on mark price to analyze price trends and manage trading risk. Supports custom intervals and time ranges for technical analysis.

Instructions

📊 合约K线数据查询 - 永续合约技术分析专用

🔍 功能说明: 获取合约市场的K线(蜡烛图)历史数据,基于标记价格生成。相比���货K线,合约K线反映永续合约的真实价格走势,去除异常波动,更适合合约交易分析和风险评估。

⚠️ 重要提醒: • 价格基准:基于标记价格,比最新成交价更稳定,减少操纵风险 • 杠杆影响:合约价格波动会被杠杆放大,需要严格风控 • 资金费率:每8小时收取资金费率,影响持仓成本 • 强平风险:价格变动可能触发强制平仓,需要监控保证金比例

🎯 适用场景: • 合约交易员制定开平仓策略和设置止盈止损 • 套利交易者分析现货-合约价差趋势 • 风险管理员监控价格波动和强平风险 • 量化策略师进行合约策略回测和优化

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

🚀 BTCUSDT合约K线数据(4小时线)

⏰ 数据时间范围:2024-01-15 08:00 ~ 2024-01-16 00:00
📈 共返回:4根K线
📉 时间间隔:4小时 (4h)

💰 最新K线详情(标记价格):
开盘价:42,890 USDT
最高价:43,255 USDT (+0.85%)
最低价:42,750 USDT (-0.33%)
收盘价:43,180 USDT
涨跌幅:+290 USDT (+0.68%)

📊 成交数据:
成交量:2,847.5 BTC
成交额:12,234.7万 USDT
成交笔数:18,456笔
主动买入量:1,623.1 BTC (占比 57.0%)

⚡ 合约特征:
• 标记价格:相比现货略微溢价
• 价格稳定:无异常跳价或操纵
• 成交活跃:流动性充足
• 趋势状态:小幅上涨,多头占优

💡 交易提示:
当前合约呈现温和上涨趋势,适合顺势操作。
建议设置止损在42,700附近,止盈可考虑43,500。
注意关注资金费率变化,当前多头占优需支付费用。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo返回K线数量。默认500,最大1000。合约交易建议:日内交易用100-200,波段交易用300-500,趋势分析用500-1000。
symbolYes必填。要查询的合约,如"BTCUSDT"永续合约。
endTimeNo查询结束时间,13位时间戳(毫秒)。不填则默认到当前时间。时间范围不要过大以免超时。
intervalYesK线时间间隔:1m=1分钟, 5m=5分钟, 15m=15分钟, 1h=1小时, 4h=4小时, 1d=1天。建议:高频交易用1m-15m,波段交易用1h-4h,趋势交易用1d-1w。
startTimeNo查询开始时间,13位时间戳(毫秒)。用于查询历史特定时间段的合约价格走势。
Behavior5/5

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

With no annotations, the description carries the full burden and discloses key behavioral traits: mark price basis, removal of abnormal fluctuations, leverage amplification, funding rate, and liquidation risk. It also includes a detailed output example showing expected structure, providing strong transparency.

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 long, with emojis, a lengthy fake output example, and trading tips that are not necessary for tool invocation. While structured with clear sections, it violates the principle that every sentence should earn its 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?

Despite no output schema, the description includes a comprehensive output example with price, volume, and market features, plus contextual warnings about leverage and funding. It fully equips the agent to understand the return data and risk factors, making it complete for a data query tool.

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 coverage is 100% and each parameter already has detailed descriptions. The description adds minor trading advice for limit and interval but does not materially enhance parameter semantics beyond what the schema provides, aligning with the baseline for high schema coverage.

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 it retrieves historical candlestick data for perpetual futures contracts based on mark price, using a specific verb+resource structure. It explicitly distinguishes from spot klines, which differentiates it from the sibling tool binance_spot_klines.

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 explicit use cases (trading strategies, arbitrage, risk management, backtesting) and positions itself as dedicated to perpetual contract technical analysis. It implies comparison with spot data but does not explicitly name alternative tools or exclusion scenarios.

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