Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz

place_order

Submit a real buy or sell order to the Nexus Exchange matching engine with limit, market, stop-loss, take-profit, and trailing order types.

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).
Install Server

TDQS

A4.2/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. It explicitly discloses 'Requires API credentials' and 'This submits a REAL order to the matching engine,' which highlights auth and live-execution risk. It also explains activation semantics for stops, take-profits, and trailing orders. It could add more about order lifecycle or rejection reasons, but the core behavioral traits are disclosed.

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 three sentences, front-loaded with the purpose, then the order-type catalog and parameter dependencies, ending with the live-order warning. Every sentence provides essential information with no redundancy or filler. Despite the complexity, it remains compact and scannable.

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?

Given the tool's complexity (10 parameters, 8 order types, no output schema), the description covers the operation, authentication, live-execution nature, and cross-parameter requirements. It does not describe the return value or error behavior, but for a place-order action the core usage is well covered. A brief note on expected response (e.g., order ID) would elevate it.

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 each parameter already has a detailed description, including the field-requirement matrix in the type parameter. The tool description repeats these requirements in prose (e.g., 'Limit-family orders require a price'), but adds no new semantic information. It consolidates the rules, but the baseline of 3 is appropriate since the schema already does the heavy lifting.

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 opens with a specific verb+resource: 'Place an order on a market, buy/sell.' It then enumerates supported order types, clearly distinguishing this from siblings like place_orders_batch (batch) and preview_order (not real). The explicit warning 'This submits a REAL order' reinforces the tool's core purpose.

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 states this places an order and requires API credentials, implying a live action. It provides detailed parameter requirements for each order family, which guides correct usage. However, it does not explicitly reference alternatives like preview_order for testing or place_orders_batch for multiple orders, so it lacks explicit when-not/exclusion guidance.

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

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/nexus-xyz/nexus-exchange-mcp'

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