Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc

binance_spot_place_order

Submit trade orders on Binance spot exchange with market, limit, stop-loss, and take-profit options. Automatically verifies balances and returns order execution details.

Instructions

【现货下单】在Binance现货市场提交交易订单

📋 功能说明

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

  • 自动验证账户余额和交易对规则

  • 实时返回订单执行状态和成交信息

⚠️ 重要提醒

  • 下单前请确保账户有足够余额

  • 市价单会立即按市场价格成交

  • 限价单需要指定价格,可能部分成交或挂单等待

🎯 适用场景

  • 购买或出售数字货币

  • 设置止盈止损策略

  • 执行套利交易策略

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

✅ 现货下单成功

📋 订单详情
订单编号:#12345678
交易对:BTCUSDT (BTC/USDT现货)
交易方向:买入 (开多仓)
订单类型:限价单
委托数量:0.001 BTC
委托价格:45,000 USDT
预计金额:45 USDT

📈 执行状态
当前状态:已提交,等待成交
已成交:0 BTC (0%)
剩余数量:0.001 BTC
下单时间:2022-01-01 08:00:00

💰 资金影响
冻结金额:45 USDT
可用余额:减少 45 USDT

⚠️ 重要提醒
订单已成功提交到交易所,请密切关注市场价格变化。
如需修改或撤销,请使用相应的撤单工具。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sideYes交易方向(必填) • BUY:买入基础资产(用计价币购买基础币) 例如:用USDT买入BTC • SELL:卖出基础资产(卖出基础币获得计价币) 例如:卖出BTC获得USDT
typeYes订单类型(必填) • MARKET:市价单,立即按当前市场价格成交 • LIMIT:限价单,指定价格挂单,等待成交 • STOP_LOSS:市价止损单,价格触发后按市价成交 • STOP_LOSS_LIMIT:限价止损单,价格触发后按限价成交 • TAKE_PROFIT:市价止盈单,价格触发后按市价成交 • TAKE_PROFIT_LIMIT:限价止盈单,价格触发后按限价成交 • LIMIT_MAKER:只做挂单方限价单,保证不会立即成交 💡 新手建议:从MARKET(市价单)或LIMIT(限价单)开始
priceNo委托价格(限价单必填,市价单无需填写) • 单位:计价资产的价格 • 例如:BTCUSDT中price表示每个BTC的USDT价格 • 必须符合交易对的价格精度要求 • 限价单:指定期望的成交价格 • 止损/止盈单:与stopPrice配合使用 💡 定价建议: - 买单价格略高于当前价:更容易成交 - 卖单价格略低于当前价:更容易成交
symbolYes交易对符号(必填) • 格式:基础资产+计价资产,如BTCUSDT、ETHUSDT • 常用交易对:BTCUSDT、ETHUSDT、BNBBUSD、ADAUSDT • 区分大小写,必须完全匹配Binance支持的交易对 • 可通过binance_exchange_info工具查看完整列表
quantityYes交易数量(必填) • 单位:基础资产的数量 • 例如:BTCUSDT中quantity表示BTC的数量 • 必须大于交易对的最小下单量 • 必须符合交易对的精度要求(小数位数) • 建议使用binance_check_order_precision工具预检查 💡 示例: - BTCUSDT最小0.00001 BTC - ETHUSDT最小0.0001 ETH
stopPriceNo触发价格(止损/止盈订单必填) • 当市场价格达到此价格时触发订单 • 仅适用于:STOP_LOSS、STOP_LOSS_LIMIT、TAKE_PROFIT、TAKE_PROFIT_LIMIT • 止损:触发价格应低于当前价格(卖单)或高于当前价格(买单) • 止盈:触发价格应高于当前价格(卖单)或低于当前价格(买单) 💡 设置建议: - 止损幅度:5-10%较为常见 - 止盈幅度:根据风险偏好设定
timeInForceNo订单有效期(可选,默认GTC) • GTC:Good Till Cancel,一直有效直到撤销或成交 • IOC:Immediate Or Cancel,立即成交可成交部分,其余撤销 • FOK:Fill Or Kill,立即全部成交,否则整单撤销 💡 使用建议: - 普通交易:使用GTC - 快速成交:使用IOC - 全部成交:使用FOK
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses that market orders execute immediately, limit orders may partially fill or wait, and funds are frozen. The output example shows order status and balance impact. However, it does not mention fee deductions, slippage, or error handling on insufficient balance.

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 headers, bullet points, and a complete output example. Every section adds value, though some redundancy with schema descriptions exists. It is front-loaded with the main action and remains readable.

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?

This is a complex place-order tool with 7 parameters and no output schema. The description covers functionality, usage scenarios, warnings, and an output example, making it comprehensive. It lacks explicit error scenarios or rate limits, but is sufficient for an agent to understand 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?

The input schema already provides 100% coverage with detailed descriptions for all 7 parameters, including examples and enums. The description adds an output example and general tips, but does not significantly enhance parameter semantics beyond what the schema already provides.

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 places orders in Binance spot market, lists supported order types, and the title '现货下单' (spot order) distinguishes it from futures order tools. It also differentiates from sibling tools like cancel order and order history by focusing on order submission.

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 includes a '适用场景' section listing when to use (buy/sell, take-profit/stop-loss, arbitrage) and a reminder about order cancellation using other tools. It also warns about balance requirements and market order behavior, but doesn't explicitly exclude futures or other 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