Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_list_orders

List and filter a user's Nobitex orders by status, type, execution, trade type, currencies, and pagination to review open or completed trades.

Instructions

List the user's orders with optional filters.

Args: status: all, open, done or close. type: buy or sell. execution: Order execution type. trade_type: spot or margin. src_currency: Source currency, e.g. "btc". dst_currency: Destination currency, e.g. "rls". details: Detail level, 1 or 2. from_id: Only orders with id >= from_id (do not combine with page). order: Sort order. page: Page number. page_size: Items per page.

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

Input Schema

NameRequiredDescriptionDefault
pageNo
typeNo
orderNo
statusNo
detailsNo
from_idNo
executionNo
page_sizeNo
trade_typeNo
dst_currencyNo
src_currencyNo

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 behavioral burden. It implies a read but never states that it is non-mutating, does not mention authentication/API-key requirements, rate limits, default page size, or what the response contains at details level 1 versus 2.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The lead sentence is front-loaded and correct, but the remainder is a mechanical Args dump that largely restates schema field names. It is not bloated, but several lines earn nothing beyond what the schema already shows.

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, no-annotation, no-output-schema tool, the definition covers parameter meanings adequately but leaves pagination semantics, return shape, and authentication expectations unaddressed. An agent can call it, but not confidently predict the result.

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%, and the description compensates by glossing all 11 parameters, adding examples for src_currency/dst_currency and the from_id/page exclusion rule that the schema does not express. Some entries are near-tautological ("order: Sort order", "execution: Order execution type") and values already enumerated in the schema are repeated, which keeps it from a 5.

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?

"List the user's orders with optional filters" gives a specific verb and resource and implies the results are scoped to the authenticated user. It is clear on its own, but it does not distinguish itself from adjacent read tools such as nobitex_list_user_trades or nobitex_list_positions.

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 only implied through the filter list; there is no statement of when to prefer this over sibling listing tools or when filters are required. The one genuinely useful rule, "do not combine with page" for from_id, is present and prevents a likely misuse.

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