kvant-binance-mcp

futures_new_order

Place a futures order on Binance with configurable type, side, quantity, and optional price or stop conditions.

Place a futures order (requires API key)

TableJSON Schema

Name	Required	Description
`side`	Yes	BUY or SELL
`type`	Yes	Order type
`price`	No	Price (required for LIMIT/STOP/TAKE_PROFIT)
`symbol`	Yes	Trading pair, e.g. BTCUSDT
`quantity`	No	Order quantity
`stopPrice`	No	Stop price for STOP/STOP_MARKET/TAKE_PROFIT orders
`reduceOnly`	No	Reduce-only order
`timeInForce`	No	Time in force (required for LIMIT)
`workingType`	No	stopPrice trigger type (default CONTRACT_PRICE)
`callbackRate`	No	Callback rate for TRAILING_STOP_MARKET (0.1-10)
`positionSide`	No	Position side. BOTH for one-way mode, LONG/SHORT for hedge mode
`closePosition`	No	Close position flag
`activationPrice`	No	Activation price for TRAILING_STOP_MARKET
`newClientOrderId`	No	Unique client order ID

B3/5.0

Behavior2/5

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

No annotations; description only states function and requirement, omitting side effects, error conditions, 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?

Single sentence is concise but lacks informative depth for a complex tool with 14 parameters.

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

Completeness2/5

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

No output schema, no explanation of return values or side effects; description is insufficient for tool complexity.

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 covers 100% of parameters with descriptions; description adds no extra value beyond schema.

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?

Description clearly states verb 'Place' and resource 'futures order', distinguishing it from sibling tools like cancel_order or account_info.

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

Usage Guidelines2/5

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

No guidance on when to use this tool vs alternatives, only mentions API key prerequisite.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/karakushan/kvant-binance-mc'

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