Skip to main content
Glama
Nobitex MCP Server

Nobitex MCP Server

by arashjfz

nobitex_get_ohlc_history

Retrieve OHLC candle history for a Nobitex market by symbol, timeframe, and time range to analyze price movement.

Instructions

Get OHLC candle history for a market.

Args: symbol: Market symbol such as BTCIRT or BTCUSDT. resolution: Candle timeframe: minutes (1,5,15,30,60,180,240,360,720) or days (D,1D,2D,3D). to: End time as a Unix timestamp in seconds. from_ts: Start time as a Unix timestamp in seconds. countback: Number of candles before to (max 500); takes priority over from_. page: Page number for older candles.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "resolution": "<resolution>",
      "to": "<to>"
    },
    "name": "nobitex_get_ohlc_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toYes
pageNo
symbolYes
from_tsNo
countbackNo
resolutionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It does disclose useful behavior beyond the name: the max of 500 candles for countback, the precedence of countback over from_ts, and that 'page' retrieves older candles, but it omits return shape, rate limits, and what happens when neither from_ts nor countback is supplied.

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

Conciseness5/5

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

One summary sentence followed by a compact, consistently formatted Args block; every line adds parameter meaning and there is no filler or repetition of the schema.

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 six-parameter tool with no annotations and no output schema, the parameter side is well covered, but the description never explains the returned candle structure or default window size, and the page/countback relationship is left implicit. Adequate but with a real gap for an agent that must interpret 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%, so the description must supply all parameter meaning and largely does: it explains symbol format, enumerates the resolution values, defines to and from_ts as Unix seconds, and gives the countback cap and precedence. The one blemish is referring to 'from_' instead of the schema's 'from_ts', plus no explanation of how page interacts with countback.

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 sentence states a specific verb and resource ('Get OHLC candle history for a market'), which is unambiguous and clearly distinct from the transaction, order, and wallet siblings. It does not, however, contrast itself with adjacent market-data tools such as nobitex_get_market_depth or nobitex_get_recent_trades, so the agent must infer which one to reach for.

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 explicit when-to-use or when-not-to-use guidance; the description only lists parameters. The only usage-adjacent statement is the precedence rule 'countback takes priority over from_', which helps choose between two params but does not route the agent between tools or state prerequisites such as symbol format validation.

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