Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz

create_order

Submit real buy or sell orders to Nexus Exchange markets with limit, market, stop-loss, take-profit, or trailing types; requires API credentials and valid pricing fields.

Instructions

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
NameRequiredDescriptionDefault
sideYesOrder side.
sizeYesOrder quantity in base units, as a positive decimal string (> 0).
typeYesOrder 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`.
priceNoLimit 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_idYesMarket id, e.g. "BTC-USDX-PERP".
reduce_onlyNoIf true, only reduces an existing position.
time_in_forceNoTime 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_priceNoTrigger 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_bpsNoFire-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_bpsNoTrailing 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.

  1. Addedv0.4.0

TDQS

A3.5/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 mostly does: it discloses that API credentials are required, warns it submits a REAL order to the matching engine, and explains how each order family fires (adverse vs favorable trigger direction, trailing retracement). Missing only secondary traits like rate limits, cancel/replace behavior, or whether submission is idempotent.

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?

Four sentences, front-loaded with the core action, then order-type coverage, then field requirements, then the credential/real-order warning. Some of the field-requirement text duplicates the schema, but nothing is padded and the highest-value warning is placed last for emphasis.

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?

For a 10-parameter mutation tool with no annotations and no output schema, the description covers order-type semantics, credential needs, and the real-order warning well. A brief note on the returned order representation (since there is no output schema) and on rate limits or error behavior would close the remaining gap.

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% and the schema itself is unusually detailed about cross-field requirements, defaults, and enum semantics. The description's consolidation of the field-requirement rules (price for limit-family, trigger_price for stops, trailing_offset_bps for trailing) largely restates the schema rather than adding new meaning, so the baseline 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Place an order on a market, buy/sell') and enumerates the eight supported order types, so the agent knows exactly what the tool does. However, it never distinguishes itself from close siblings in the list such as `place_order`, `create_orders`/`place_orders_batch`, or `preview_order`, which is the main thing an agent needs to disambiguate here.

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?

There is no explicit 'use this when' guidance and no mention of alternatives, even though `preview_order`, `place_order`, and the batch variants sit right beside it. The implicit signal that this is a real single-order submission is present ('submits a REAL order'), but the agent is left to infer routing itself.

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

Deploy Server

Other Tools