Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_futures_place_order

Place orders on Binance perpetual futures with market, limit, stop, and take-profit types. Configure symbol, side, quantity, and risk parameters for effective trading.

Instructions

【合约下单】在Binance永续合约市场提交交易订单

📋 功能说明

  • 支持USDT永续合约和币本位合约交易

  • 包括开仓、平仓、加仓、减仓等操作

  • 支持多种订单类型:市价、限价、止损、止盈

  • 自动计算保证金需求和风险参数

⚠️ 重要提醒

  • 合约交易具有高风险,可能导致全部本金亏损

  • 下单前请确保账户有足够保证金

  • 建议设置合理的止损止盈策略

  • 注意杠杆倍数对风险的放大效应

🎯 适用场景

  • 看多看空某个资产的价格走势

  • 利用杠杆放大投资收益

  • 对冲现货持仓风险

  • 执行量化交易策略

📊 输出示例 成功下单后将返回:

🚀 合约下单成功

📋 订单详情
订单编号:#123456789
合约类型:BTCUSDT 永续合约
交易方向:买入开多仓 (看涨)
订单类型:限价单
委托数量:0.001 BTC
委托价格:45,000 USDT
下单时间:2022-01-01 08:00:00

📈 执行状态
当前状态:已提交,等待成交
已成交:0 BTC (0%)
剩余数量:0.001 BTC
预计成交金额:45 USDT

💰 保证金情况
使用杠杆:10倍 (高风险)
所需保证金:4.5 USDT
账户余额:1,000 USDT
可用余额:995.5 USDT
保证金率:0.45%

📊 盈亏预测
盈亏平衡点:45,000 USDT
上涨10%盈利:+45 USDT (1000%收益)
下跌10%亏损:-45 USDT (-1000%亏损)

⚠️ 风险提醒
合约交易具有极高风险,10倍杠杆可能导致快速爆仓!
强烈建议设置止损价格,控制风险敞口。
密切关注市场变化,及时调整策略。

🎯 建议操作
- 立即设置止损订单
- 关注强制平仓价格
- 准备应急平仓方案

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYes交易方向(必填) • BUY:买入方向 - 单向持仓:开多仓或平空仓 - 双向持仓:增加多头持仓 • SELL:卖出方向 - 单向持仓:开空仓或平多仓 - 双向持仓:增加空头持仓 💡 方向选择: - 看涨:选择BUY开多仓 - 看跌:选择SELL开空仓
typeYes订单类型(必填) • MARKET:市价单,立即按当前价格成交 • LIMIT:限价单,指定价格挂单等待成交 • STOP:限价止损单,触发后按限价成交 • TAKE_PROFIT:限价止盈单,触发后按限价成交 • STOP_MARKET:市价止损单,触发后按市价成交 • TAKE_PROFIT_MARKET:市价止盈单,触发后按市价成交 💡 类型选择: - 快速成交:MARKET - 精确价格:LIMIT - 风险管理:STOP/TAKE_PROFIT
priceNo委托价格(限价单必填) • 仅限价单(LIMIT、STOP、TAKE_PROFIT)需要 • 市价单无需填写此参数 • 必须符合价格精度要求 • 建议参考当前标记价格设定 💡 价格策略: - 开多:价格略高于当前价更易成交 - 开空:价格略低于当前价更易成交 - 止损:设置合理的风险承受范围
symbolYes合约交易对(必填) • USDT永续合约:如BTCUSDT、ETHUSDT • 币本位合约:如BTCUSD_PERP、ETHUSD_PERP • 区分大小写,必须完全匹配Binance支持的合约 • 可通过binance_exchange_info查看完整列表 💡 合约选择: - 新手推荐:USDT永续合约(如BTCUSDT) - 高级用户:币本位合约(如BTCUSD_PERP)
quantityYes交易数量(必填) • 基础资产的数量,如BTCUSDT中表示BTC数量 • 必须符合合约的最小下单量要求 • 必须符合精度要求(小数位数) • 建议使用binance_check_order_precision预检查 💡 数量计算: - BTCUSDT最小:0.001 BTC - ETHUSDT最小:0.001 ETH - 注意区分张数和价值
stopPriceNo触发价格(止损止盈单必填) • 当标记价格达到此价格时触发订单 • 仅用于STOP和TAKE_PROFIT类订单 • 止损:触发价格应低于入场价(多头) • 止盈:触发价格应高于入场价(多头) 💡 设置建议: - 止损:3-5%的价格回撤 - 止盈:根据风险收益比设定
reduceOnlyNo只减仓模式(可选,默认false) • true:只减仓单,只能减少持仓,不能增加 • false:普通单,可开仓或平仓 • 平仓时建议设为true避免过度开仓 • 用于风险控制和精确平仓 💡 使用场景: - 平仓操作:设为true - 开仓操作:设为false
timeInForceNo订单有效期(可选,默认GTC) • GTC:Good Till Cancel,一直有效直到撤销 • IOC:Immediate Or Cancel,立即成交可成交部分 • FOK:Fill Or Kill,立即全部成交,否则撤销 • GTX:Good Till Crossing,只挂单不成交 💡 选择建议: - 普通交易:GTC - 快速成交:IOC - 全部成交:FOK
positionSideNo持仓方向(可选,默认BOTH) • BOTH:单向持仓模式(推荐新手) - 同一合约只能持有一个方向 - 操作简单,风险控制清晰 • LONG:多头方向(双向持仓模式) - 专门用于多头操作 • SHORT:空头方向(双向持仓模式) - 专门用于空头操作 💡 模式建议: - 新手:使用BOTH模式 - 对冲需求:使用LONG/SHORT模式
closePositionNo全仓平仓(可选,默认false) • true:市价全平该方向的所有持仓 • false:按指定数量下单 • 设为true时会忽略quantity参数 • 适用于紧急平仓或一键清仓 💡 使用场景: - 紧急平仓:设为true - 部分平仓:设为false并指定quantity
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses risk warnings (high risk, margin needs, leverage amplification), mentions '自动计算保证金需求和风险参数', and includes a detailed output example showing execution status, margin details, PnL predictions, and suggested actions. This goes beyond simple 'places order' and describes order lifecycle behavior. However, it does not mention error handling or rate limits.

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 long and uses multiple sections with headers and emojis, but the output example is very verbose (about 30 lines) and could be trimmed for conciseness. The structure is organized and readable, but not every sentence clearly earns its place in a tool description.

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

Completeness4/5

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

Given 10 parameters, no annotations, and no output schema, the description is quite comprehensive. It covers purpose, usage scenarios, risk warnings, and provides an illustrative output. It indirectly references other tools in the schema (exchange info, precision check). Missing error scenarios or authentication details, but overall it gives sufficient context for an agent to select and invoke the 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 description coverage is 100% with detailed per-parameter explanations, including enums, examples, and tips. The tool description adds no specific parameter semantics beyond restating order types and auto-calculating margin. It relies on the schema for parameter meaning, which is the expected baseline when coverage is high.

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 explicitly states the tool submits trading orders on Binance perpetual futures ('在Binance永续合约市场提交交易订单'), enumerates supported operations (open/close/add/reduce positions) and order types (market, limit, stop, take-profit). This specific verb+resource combination distinguishes it from spot trading and sibling tools like binance_spot_place_order.

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 clear contexts: bullish/bearish speculation, leverage amplification, hedging spot positions, and quant trading. It implicitly indicates futures usage but does not explicitly name alternatives or state when not to use this tool. Cross-references to exchange info appear in the schema, not the description.

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