Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_cancel_order

Cancel a single open order on Nobitex using a server order ID or client order ID, enabling AI agents to close active trades.

Instructions

Cancel a single open order.

Args: order: Server order id. client_order_id: Client order id.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "nobitex_cancel_order"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderNo
client_order_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3/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 disclosure burden, yet it says nothing about irreversibility, what happens if the order is already filled or partially filled, auth/API-key requirements, rate limits, or what is returned. 'Cancel' signals a destructive mutation but the consequences and failure modes are entirely undisclosed.

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 summary is front-loaded and the Args block is compact. Slight redundancy in restating parameter names, but the docstring-style layout is scannable and contains no filler.

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 a mutation tool with zero annotations, no output schema, and two all-optional identifiers, the definition leaves critical gaps: it never states that at least one identifier must be provided, what success/failure looks like, or whether cancellation is final. An agent could easily call this with both arguments null.

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 coverage is 0% and the schema itself only offers bare integer/string titles, so the description's gloss 'order: Server order id' versus 'client_order_id: Client order id' meaningfully separates the exchange-side identifier from the client-side one — a distinction the agent could not make from the schema. It still fails to say which identifier is required or how to choose when both are supplied.

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?

States a specific verb and resource plus scope: 'Cancel a single open order.' The word 'single' implicitly separates it from bulk siblings like nobitex_cancel_old_orders, but no sibling is named explicitly, so the agent must infer the distinction from tool names 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 when-to-use guidance, no mention of alternatives (bulk cancel, emergency cancel), and no prerequisites such as the order needing to be in an open/unfilled state. The only usage signal is the 'single open order' scope phrase.

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