Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_cancel_old_orders

Cancel multiple open orders older than a specified number of hours, with optional filters for execution type, spot or margin, and source/destination currencies to remove stale orders.

Instructions

Cancel old open orders in bulk.

Args: hours: Cancel orders older than this many hours. execution: Filter by execution type. trade_type: Filter by spot or margin. src_currency: Filter by source currency. dst_currency: Filter by destination currency.

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

Input Schema

NameRequiredDescriptionDefault
hoursNo
executionNo
trade_typeNo
dst_currencyNo
src_currencyNo

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 supplied, so the description carries the full behavioral burden for an irreversible bulk mutation, and it does not state that cancellation cannot be undone, whether the operation is atomic, what permissions or API key scopes are needed, or what the response contains. The only behavioral hint is the word "bulk," which is far short of what a destructive no-annotation tool requires.

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 summary sentence is front-loaded and the Args list is terse with no filler. Structure is clear and every line maps to a parameter, though the list could have been folded into a more scannable form.

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 five-parameter destructive bulk operation with no annotations and no output schema, the definition should clarify default behavior when filters are omitted, reversibility, and return shape. None of these are covered, leaving meaningful gaps for an agent deciding whether it is safe to call.

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%, and the Args block does give a one-line meaning for each of the five parameters, which is genuine value beyond the bare schema. However, it omits important semantics: currency format/casing, timezone for "hours," and—most importantly—the effect of leaving each filter null.

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 first line gives a specific verb and resource ("Cancel old open orders in bulk"), which distinguishes it from single-order cancellation like nobitex_cancel_order via the words "bulk" and "old". It doesn't explicitly name a sibling alternative, so it stops short of a 5.

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?

The description never says when to prefer this over nobitex_cancel_order or the emergency-cancel tools, and gives no prerequisites. Critically, it doesn't explain what happens when filters are omitted (all five params are optional), which leaves the agent unable to judge whether calling with no args would mass-cancel everything.

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