Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_place_spot_order

Place buy or sell spot orders on Nobitex with limit, market, stop-limit, or stop-market execution, including optional OCO and client order IDs.

Instructions

Place a spot order.

Args: type: Order side, "buy" or "sell". src_currency: Source/base currency, e.g. "btc". dst_currency: Destination/quote currency, e.g. "usdt" or "rls". amount: Order size in src_currency, as a decimal string. execution: "limit" (default), "market", "stop_limit" or "stop_market". price: Unit price; required for limit/stop_limit. Decimal string. client_order_id: Optional unique client id (max 32 chars). pro: Disable the 10-second duplicate-order check. mode: Set "oco" for an OCO order. stop_price: Trigger price for stop orders / OCO. stop_limit_price: Paired stop-limit price for OCO.

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_spot_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
proNo
modeNo
typeYes
priceNo
amountYes
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.1/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 behavioral burden and mostly does not: it never says this commits real funds, what permissions are needed, what happens on insufficient balance, or what the call returns (order id, status). The one genuinely behavioral disclosure is that pro disables the 10-second duplicate-order check, which is useful but isolated.

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 the per-argument list is terse with no filler sentences. The docstring "Args:" framing is mechanical but does not waste tokens.

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

Completeness3/5

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

For an 11-parameter, funds-moving mutation with no annotations and no output schema, the definition covers inputs well but leaves out what an agent most needs around the call: response shape, failure modes, and the OCO interaction rules. The input side is complete enough to invoke correctly; the outcome side is not described at all.

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: it defines each of the 11 parameters, marks price as required for limit/stop_limit, states the execution default, specifies decimal-string formatting and the 32-char cap on client_order_id. It falls short on the OCO relationship between mode, stop_price and stop_limit_price, and on any amount/price bounds.

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?

"Place a spot order" gives a specific verb and resource, and the args list makes the domain (currency pairs, order types) concrete. It does not explicitly contrast itself with the sibling nobitex_place_margin_order, so the spot-vs-margin distinction is left for the agent to infer from the word "spot" alone.

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 statement of when to choose this over nobitex_place_margin_order, no prerequisites (funding, API key scope, whitelist), and no note on when an OCO or stop order should be used instead of a plain limit/market order. The only conditional guidance is embedded in parameter notes (price required for limit/stop_limit), which is invocation detail rather than usage routing.

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