Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_order_status

Retrieves the status of a single order using either its server order ID or client order ID, helping you track order progress and verify its current state.

Instructions

Get the status of one order by id or client order id.

Args: id: 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_get_order_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNo
client_order_idNo

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 behavioral burden. It implies a read-only lookup but does not state what is returned (status values, fill state, error behavior when the order is unknown), nor what happens if both identifiers are given or neither is given. For a tool with zero annotation coverage this is a substantial gap.

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 block is compact with no filler. The only inefficiency is that the Args block restates parameter names without adding much beyond the schema titles.

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?

With no output schema and no annotations, the description should explain the shape of the returned status and the identifier requirement. It does neither, so an agent cannot fully predict the response or the valid call forms for this two-parameter tool.

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 compensate, and it does partially by glossing id as 'Server order id' and client_order_id as 'Client order id'. However it does not explain precedence when both are supplied, nor that one is effectively required, so the semantics remain incomplete.

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 ('Get the status of one order') and names the two lookup keys, which is enough to distinguish it from siblings like nobitex_cancel_order or nobitex_place_spot_order. It stops short of explicitly contrasting itself with any sibling, so it is clear but not maximally differentiated.

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 prerequisites, and no statement of the alternative path (e.g. use cancel_order to change state rather than inspect it). Critically, both parameters are optional in the schema, yet the description never says that at least one of id or client_order_id must be supplied, leaving the agent to infer the calling contract.

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