Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_close_position

Closes or settles a Nobitex margin position using market, limit, stop-market, or stop-limit execution, with optional amount, price, and stop trigger settings.

Instructions

Close (settle) a margin position.

Args: position_id: Position id. execution: Close execution type; "market" closes at best price. amount: Amount to settle as a decimal string. price: Limit price for limit/stop_limit closes. stop_price: Trigger price for stop closes. stop_limit_price: Paired stop-limit price. client_order_id: Optional client order id.

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": {
      "position_id": "<position_id>"
    },
    "name": "nobitex_close_position"
  }
}

Input Schema

NameRequiredDescriptionDefault
priceNo
amountNo
executionNomarket
stop_priceNo
position_idYes
client_order_idNo
stop_limit_priceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for a destructive financial mutation, yet it says nothing about irreversibility, fees, whether the close can be partial, or what happens if position_id is invalid or already closed. The one useful disclosure is that execution="market" closes at best price, but the default of "market" and the consequences of omitting optional fields are left unstated.

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 purpose statement is front-loaded in one sentence, followed by a compact param list; nothing is redundant. The docstring-style Args block is functional but reads as raw schema annotation rather than curated guidance.

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 a seven-parameter, order-placing mutation with no annotations and no output schema, the description covers only parameter names and the market-close behavior. It leaves out permission requirements, partial-vs-full close semantics, conditional parameter dependencies, and any indication of what a successful close returns.

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 0%, so the description must do the work, and it does document all seven parameters with at least a phrase each, including the useful conditional links (price for limit/stop_limit, stop_price for stop closes, stop_limit_price as paired). However several entries are tautological ("position_id: Position id"), and it omits that amount is optional, that only position_id is required, and that execution defaults to market — leaving conditional requirements and defaults for the agent to infer.

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?

"Close (settle) a margin position" gives a specific verb plus resource, which clearly separates it from siblings like nobitex_edit_position_collateral and nobitex_get_position_status. It stops short of 5 because it never explicitly contrasts itself with those siblings or states the scope of what 'settle' means (full vs. partial).

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 when-to-use or when-not guidance, no prerequisites such as an open margin position or required permissions, and no mention of alternatives for adjusting rather than closing a position. The only implied usage comes from the parameter list 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