Skip to main content
Glama
Muvon

mcp-binance-futures

by Muvon

place_order

Execute futures trades on Binance by placing market, limit, or conditional orders like stop-loss and take-profit to manage positions.

Instructions

Place a new futures order.

ORDER TYPE GROUPS — choose the right one:

Immediate orders (fill now or queue at price): MARKET: side=BUY, quantity=0.01 LIMIT: side=SELL, quantity=0.01, price=50000, time_in_force=GTC

Conditional orders (wait for stop_price trigger, then execute): Stop-loss full close: side=SELL, type=STOP_MARKET, stop_price=45000, close_position=True Take-profit full close: side=SELL, type=TAKE_PROFIT_MARKET, stop_price=60000, close_position=True Stop-loss partial: side=SELL, type=STOP_MARKET, stop_price=45000, quantity=0.01, reduce_only=True Trailing stop: side=SELL, type=TRAILING_STOP_MARKET, stop_price=45000, quantity=0.01, callback_rate=1.0

IMPORTANT — close_position=True vs quantity+reduce_only: close_position=True → closes the ENTIRE position, no quantity needed, max 1 SL + 1 TP active at a time. reduce_only=True → closes a PARTIAL quantity, multiple allowed simultaneously. Never mix both on the same order.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYesTrading pair, e.g. 'BTCUSDT'
sideYesOrder direction
order_typeYesOrder type. Two distinct groups with different rules: ENTRY/EXIT orders (placed immediately, quantity required): MARKET — executes at current market price LIMIT — executes at `price` or better; requires price + time_in_force CONDITIONAL orders (wait for trigger, routed to Algo API): STOP_MARKET — market exit when price hits stop_price (stop-loss) TAKE_PROFIT_MARKET — market exit when price hits stop_price (take-profit) STOP — limit exit at `price` when stop_price is hit TAKE_PROFIT — limit exit at `price` when stop_price is hit TRAILING_STOP_MARKET — trails price by callback_rate %
quantityNoOrder quantity in base asset. Required for MARKET, LIMIT, STOP, TAKE_PROFIT, TRAILING_STOP_MARKET, and conditional orders without close_position=True. Omit only when using close_position=True (closes the full position).
priceNoLimit fill price. Required for LIMIT, STOP, TAKE_PROFIT.
stop_priceNoTrigger price. Required for all conditional types: STOP, STOP_MARKET, TAKE_PROFIT, TAKE_PROFIT_MARKET, TRAILING_STOP_MARKET.
time_in_forceNoTime in force. Required for LIMIT. Optional for conditional orders (default GTC).
reduce_onlyNoIf True, order can only reduce an existing position (partial close). Use this with a specific quantity to partially close. Cannot be combined with close_position=True.
close_positionNoIf True, closes the ENTIRE position when triggered (Close-All). Only valid with STOP_MARKET or TAKE_PROFIT_MARKET. Do NOT send quantity. Binance allows at most 1 active close_position=True order per type per direction — cancel the existing one first before placing a replacement.
position_sideNoRequired in Hedge Mode. Use BOTH for One-way mode.
client_order_idNoOptional custom order ID (max 36 chars).
callback_rateNoTrailing stop callback rate in % (0.1–10). Only for TRAILING_STOP_MARKET.

Output 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 and does so comprehensively. It explains critical behavioral traits: order execution timing (fill now vs wait for trigger), routing differences (conditional orders go to Algo API), position management rules (close entire vs partial position), and platform-specific constraints (max 1 SL + 1 TP active at a time, Binance limitations).

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 well-structured with clear headings and bullet points, making complex information digestible. While somewhat lengthy due to the tool's complexity, every section (order type groups, examples, important rules) serves a clear purpose. The front-loaded purpose statement is followed by logically organized supporting 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?

For a complex 12-parameter trading tool with no annotations, the description provides exceptional completeness. It covers purpose, usage scenarios, behavioral characteristics, parameter relationships, and platform-specific constraints. The presence of an output schema means the description doesn't need to explain return values, allowing it to focus entirely on the critical operational knowledge needed to use this 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?

Schema description coverage is 100%, so the baseline would be 3. However, the description adds significant value beyond the schema by providing concrete examples with actual parameter values for different order types, clarifying the relationships between parameters (like how close_position=True interacts with quantity), and explaining the practical implications of parameter combinations through the order type groups.

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 immediately states the specific action ('Place a new futures order') with clear verb+resource. It distinguishes this tool from all sibling tools (like cancel_order, modify_order, get_open_orders) by focusing on order creation rather than modification, cancellation, or querying.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit guidance on when to use different order type groups (Immediate vs Conditional orders) and includes critical usage rules about close_position=True vs quantity+reduce_only. It clearly distinguishes between different scenarios and warns against invalid combinations ('Never mix both on the same order').

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/Muvon/mcp-binance-futures'

If you have feedback or need assistance with the MCP directory API, please join our Discord server