nexus-exchange-mcp

Official

Overview Schema Source Related Servers Discussions Admin

place_order

Submit real buy/sell orders to Nexus Exchange (limit, market, stop-loss, take-profit, trailing). Deprecated: use create_order.

Instructions

Deprecated: use create_order. Place an order on a market, buy/sell. Supports limit, market, stop-loss (stop_limit / stop_market), take-profit (take_profit_limit / take_profit_market), and trailing (trailing_stop / trailing_limit) orders. Limit-family orders require a price; stop / take-profit orders require a trigger_price; trailing orders require trailing_offset_bps (and trailing_limit also limit_offset_bps). Requires API credentials. This submits a REAL order to the matching engine.

Input Schema

TableJSON Schema

Name	Required	Description
`side`	Yes	Order side.
`size`	Yes	Order quantity in base units, as a positive decimal string (> 0).
`type`	Yes	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`.
`price`	No	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).
`market_id`	Yes	Market id, e.g. "BTC-USDX-PERP".
`reduce_only`	No	If true, only reduces an existing position.
`time_in_force`	No	Time in force. Defaults to GTC for limit, IOC for market. `PostOnly` rejects the order if it would take liquidity on entry, guaranteeing it rests as a maker.
`trigger_price`	No	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.
`limit_offset_bps`	No	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.
`trailing_offset_bps`	No	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).

Schema Changelog

Changes observed during successful MCP inspections.

Changed6 schema fields changedv0.2.0Aug 19, 2026

addedInput schema / 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 / 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 / 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 / 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 / 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 / type / enum

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

Changed4 schema fields changedJul 16, 2026

changedInput schema / properties / price / description

Previous value: -"Limit price as a string. Required for limit orders, ignored for market."New value: +"Limit price as a positive decimal string (> 0). Required for limit orders, ignored for market."

changedInput schema / properties / size / description

Previous value: -"Order quantity in base units, as a string."New value: +"Order quantity in base units, as a positive decimal string (> 0)."

changedInput schema / properties / time_in_force / description

Previous value: -"Time in force. Defaults to GTC for limit, IOC for market."New value: +"Time in force. Defaults to GTC for limit, IOC for market. `PostOnly` rejects the order if it would take liquidity on entry, guaranteeing it rests as a maker."

changedInput schema / properties / time_in_force / enum

Previous value: -[
-  "GTC",
-  "IOC",
-  "FOK"
-]New value: +[
+  "GTC",
+  "IOC",
+  "FOK",
+  "PostOnly"
+]

First observedv0.1.0Jun 23, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations, the description carries the full burden and discloses key traits: it requires API credentials, it submits a REAL order to the matching engine, and it explains trigger/fire semantics for stop, take-profit, and trailing orders. It stops short of stating rate limits, idempotency behavior, or error conditions, keeping it below a 5.

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?

Front-loads the deprecation warning, then the operation, then the type/field matrix in dense, information-rich sentences. It is longer than ideal and duplicates some schema content, but nearly every clause earns its place for a complex 10-parameter tool.

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?

Covers deprecation, credential requirements, real execution, and conditional parameter requirements for a complex tool with no output schema. It omits return values (order id/response shape) and any idempotency or rate-limit context, which keeps it from a 5.

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%, so the schema already documents each parameter, including field requirements per order type. The description's parameter recap (which type requires which field) largely restates the schema rather than adding new meaning, so the baseline of 3 is appropriate.

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?

States a specific verb+resource ('Place an order on a market, buy/sell') and immediately flags deprecation in favor of `create_order`, distinguishing it from siblings like preview_order and create_order. An agent can identify both what it does and that a preferred replacement exists without opening the schema.

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?

Explicitly names the alternative ('Deprecated: use `create_order`') and gives the condition that selects it. It also specifies per-order-type usage rules (when `price`, `trigger_price`, `trailing_offset_bps`, and `limit_offset_bps` apply), so an agent knows exactly when and how to invoke it.

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

Deploy Server

place_order

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools