Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_orderbook

Retrieve the level-2 order book for a specific market or all markets to analyze market depth and liquidity.

Instructions

Get the level-2 order book for one market or all markets.

Args: symbol: Market symbol such as BTCIRT or BTCUSDT, or "all".

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

Input Schema

NameRequiredDescriptionDefault
symbolNoall

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/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, and it discloses very little. 'Level-2 order book' tells the agent the depth-of-book semantics, but nothing is said about whether the call needs authentication, whether the response is a snapshot or streaming, pagination/row limits, or rate limits. For a market-data tool with zero annotation coverage this is a notable 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 operational sentence is front-loaded and wastes no words. The 'Args:' block is a docstring artifact and slightly redundant with the front matter, but it is short and does not bury the key information.

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 single-parameter read tool with no output schema and no annotations, the description covers purpose, scope, and symbol format adequately. It is still thin on what the returned order book looks like (bid/ask levels, count, ordering) and on whether 'all' markets returns a keyed map, which an agent would want before calling.

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% — the schema only exposes a bare string named 'symbol' with default 'all'. The description compensates well, giving example values (BTCIRT, BTCUSDT) and clarifying that the literal string 'all' is a valid selector meaning every market. That is real meaning added beyond the structured field.

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 description uses a specific verb and resource ('Get the level-2 order book') and states the scope ('one market or all markets'), which is far more informative than the bare name. It does not distinguish itself from the closely-named sibling nobitex_get_market_depth, 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?

There is no guidance on when to choose this tool over nobitex_get_market_depth, nobitex_get_market_stats, or nobitex_get_recent_trades, all of which could plausibly return market data. The only implied usage is the 'all vs one market' choice, and even that is described as a parameter behavior rather than a selection rule.

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