Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz

preview_order

Check the margin, equity, and fee impact of an order before submitting it. Simulate order placement without anything reaching the matching engine.

Instructions

Preview an order without submitting it: projects the margin, equity, and fee impact of the order. Takes the same arguments as place_order. Nothing reaches the matching engine. Requires API credentials.

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?

No annotations exist, so the description carries the full disclosure burden—and it delivers: it reveals the no-side-effect guarantee ('Nothing reaches the matching engine'), the nature of outputs (margin/equity/fee projection), and auth requirements ('Requires API credentials'). This adds genuine behavioral context beyond the name.

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?

Four terse sentences, each earning its place: purpose+outputs, parameter parity reference, safety guarantee, and auth requirement. Front-loaded with the main verb and immediately informative.

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, annotation-free, output-schema-less tool, the description covers the essentials: behavior, outputs, safety profile, auth, and parameter parity with place_order. Returning projection details (margin/equity/fees) partially compensates for the missing output schema. Could mention error behavior or rate limits, but adequate as-is.

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 baseline of 3 applies. The description adds a small cross-tool semantic note ('Takes the same arguments as place_order') establishing parameter parity, but the schema's own descriptions do the heavy lifting for the 10 parameters.

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?

Specific verb+resource: 'Preview an order without submitting it' with a clear statement of outputs ('projects the margin, equity, and fee impact'). It explicitly names the sibling `place_order` and differentiates via 'Nothing reaches the matching engine,' leaving no ambiguity about what this 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?

'Without submitting it' plus 'Nothing reaches the matching engine' clearly signals the safe-to-test use case, and 'Takes the same arguments as place_order' names the primary alternative. Lacks an explicit when-not-to statement or named alternatives beyond place_order, but the context is strong.

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