nexus-exchange-mcp

Official

Overview Schema Source Related Servers Discussions Admin

place_orders_batch

Submit multiple real exchange orders in one batch request, using place_order parameters for each. Send 1–100 market, limit, stop, take-profit, or trailing orders at once.

Instructions

Submit multiple orders in one request. Each order has the same shape as place_order (market_id, side, type, size, and the type-dependent price / trigger_price / trailing offsets / time_in_force / reduce_only). Requires API credentials. This submits REAL orders to the matching engine.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`orders`	Yes	Orders to submit (1–100). Each uses the place_order arg shape.

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.0Aug 19, 2026

addedInput schema / properties / orders / items / properties / limit_offset_bps

Added value: +{
+  "description": "Fire-time limit-price offset in basis points (`trailing_limit` only; required together with `trailing_offset_bps`). The rested limit sits at fire_price * (1 + offset) for buys / * (1 - offset) for sells; 0 rests exactly at the fire price.",
+  "maximum": 9999,
+  "minimum": 0,
+  "type": "integer"
+}

changedInput schema / properties / orders / items / properties / price / description

Previous value: -"Limit price as a positive decimal string (> 0). Required for limit orders, ignored for market."New value: +"Limit price as a positive decimal string (> 0). Required for limit-family orders (`limit`, `stop_limit`, `take_profit_limit`); must be omitted for market, stop_market, take_profit_market, and trailing orders (which are priced by the engine or computed at fire time)."

addedInput schema / properties / orders / items / properties / trailing_offset_bps

Added value: +{
+  "description": "Trailing trigger offset in basis points (1 bp = 0.01%). Required for trailing orders (`trailing_stop`, `trailing_limit`); must be omitted otherwise. Fires once the mark price retraces from its best-seen extreme by this many bps (0 fires at the first evaluation).",
+  "minimum": 0,
+  "type": "integer"
+}

addedInput schema / properties / orders / items / properties / trigger_price

Added value: +{
+  "description": "Trigger threshold as a positive decimal string (> 0). Required for stop and take-profit orders (`stop_limit`, `stop_market`, `take_profit_limit`, `take_profit_market`): the order activates once the mark price crosses it — adversely for stops, favorably for take-profits. Must be omitted for other order types.",
+  "type": "string"
+}

changedInput schema / properties / orders / items / properties / type / description

Previous value: -"Order type."New value: +"Order type. `limit` and `market` are unconditional. `stop_limit` / `stop_market` fire when the mark price crosses `trigger_price` in the adverse direction (stop-loss); `take_profit_limit` / `take_profit_market` fire on the favorable direction. `trailing_stop` fires a market order once the mark retraces from its best-seen extreme by `trailing_offset_bps`; `trailing_limit` fires the same way but rests a limit order priced off the fire price by `limit_offset_bps`. Field requirements: limit-family (`limit`, `stop_limit`, `take_profit_limit`) require `price`; stop / take-profit types require `trigger_price`; trailing types require `trailing_offset_bps`."

changedInput schema / properties / orders / items / properties / type / enum

Previous value: -[
-  "limit",
-  "market"
-]New value: +[
+  "limit",
+  "market",
+  "stop_limit",
+  "stop_market",
+  "take_profit_limit",
+  "take_profit_market",
+  "trailing_stop",
+  "trailing_limit"
+]

AddedJul 16, 2026

TDQS

A4.2/5.0

Behavior4/5

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

With no annotations present, the description carries the burden of disclosure. It explicitly states 'Requires API credentials' and 'This submits REAL orders to the matching engine,' which is strong mutation/side-effect warning. It does not mention batch atomicity, partial failures, or return behavior, but the most critical risk is addressed.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is brief and front-loaded, with three sentences that each carry meaningful info: what it does, how the order shape is derived, and the real-order behavior. The parenthetical field list is dense but aids completeness without bloating the text.

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?

The rich nested schema covers the parameter semantics thoroughly. The description adds the missing non-schema information: credential requirements and real trading side effects. It does not explain batch-level behavior such as atomicity or failure handling, but overall it gives an agent enough context to invoke the tool correctly.

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 the nested order properties are extensively documented. The description adds convenience by referencing the `place_order` shape, but it does not add substantive new semantics beyond what the schema already provides, so the baseline 3 applies.

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 uses a specific verb ('Submit'), names the resource ('multiple orders in one request'), and clearly distinguishes the tool from the sibling `place_order` by emphasizing batch capability. It also summarizes the relevant order fields, leaving no ambiguity about what the tool does.

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 clearly implies this is the batched counterpart to `place_order`, giving context that it should be used when submitting multiple orders together. It does not explicitly state when-not to use it or name alternatives, but the intended usage is clear from the wording.

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

Deploy Server

place_orders_batch

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools