Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_place_margin_order

Place a leveraged margin order on Nobitex with limit, market, stop, or OCO execution. Specify side, currency pair, amount, price, and leverage to open or close positions.

Instructions

Place a margin (leverage) order.

Args: type: Order side, "buy" or "sell". src_currency: Base currency, e.g. "btc". dst_currency: Quote currency, e.g. "usdt". amount: Order size as a decimal string. execution: "limit", "market", "stop_limit" or "stop_market". price: Limit price (required for limit/stop_limit). stop_price: Trigger price (required for stop orders / OCO). stop_limit_price: Paired stop-limit price (required for OCO). leverage: Leverage multiplier as a string, e.g. "2". client_order_id: Optional unique client id. mode: Set "oco" for an OCO order.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "type": "<type>",
      "src_currency": "<src_currency>",
      "dst_currency": "<dst_currency>",
      "amount": "<amount>"
    },
    "name": "nobitex_place_margin_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNo
typeYes
priceNo
amountYes
leverageNo
executionNolimit
stop_priceNo
dst_currencyYes
src_currencyYes
client_order_idNo
stop_limit_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It says nothing about what placing an order does to funds, whether market orders fill immediately, whether the order can be cancelled afterward, or what error conditions (insufficient margin, invalid leverage) look like. The only behavioral hint is that fields become conditionally required, which is helpful but limited.

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?

The one-line purpose is front-loaded and each argument gets exactly one line with no filler. The docstring-style 'Args:' listing is slightly raw but efficient and scannable.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an 11-parameter financial mutation with no annotations and no output schema, the definition covers inputs well but omits leverage limits and prerequisites, the semantics of an OCO pair at runtime, and what the call returns (order id, status). An agent could construct the call but not predict or interpret the outcome.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate, and it largely does: all 11 parameters are explained with examples ('btc', 'usdt', '2') and the conditional requirements are spelled out (price for limit/stop_limit, stop_price for stop/OCO, stop_limit_price for OCO). The main gap is that the interaction between execution and the stop fields is described per-field rather than as a coherent rule set.

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?

The opening line states a specific verb and resource (place a margin/leverage order), and the parenthetical 'leverage' distinguishes it from a plain spot order. It stops short of explicitly naming nobitex_place_spot_order as the alternative, so the differentiation is implied rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the name and the parameter list, but there is no explicit guidance on when to choose a margin order over a spot order, no mention of leverage prerequisites, and no reference to nobitex_get_margin_delegation_limit for checking available leverage.

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