Skip to main content
Glama
tjackiet

bitbank-mcp-server

by tjackiet

get_candles

Retrieve historical candlestick data (OHLCV) for specified trading pairs and timeframes, with filters for date, limit, and timezone.

Instructions

[Candles / OHLCV / Candlestick] ローソク足(candles / OHLCV / chart data)を取得。1min〜1monthの各時間足に対応。date は tz(既定 Asia/Tokyo)の暦日として解釈し、その終端以前の limit 本を返す。 詳細は inputSchema を参照。

【重要】バックテストには run_backtest を使用(データ取得〜チャート描画を一括実行)。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNoタイムゾーン(既定 Asia/Tokyo)。date パラメータの暦日解釈、isoTimeLocal、keyPoints.date、priceRange.periodStart/End の表示に使用。isoTime は常に UTC ISO。空文字も Asia/Tokyo にフォールバック。UTC が必要な場合は明示的に "UTC" を渡す。Asia/Tokyo
dateNotype により形式が異なる: - 1min/5min/15min/30min/1hour → YYYYMMDD(例: 20251022) - 4hour/8hour/12hour/1day/1week/1month → YYYY(例: 2025) date=YYYYMMDD は tz(既定 Asia/Tokyo)の暦日として解釈します。指定日の終端(23:59:59.999 in tz)以前の limit 本を返します。limit は日数ではなくローソク足本数です。例: 1hour, date=20251002, limit=24 は指定 tz の 10/2 24 本(00:00〜23:00)。 省略時は最新。 (互換: 年足系で YYYYMMDD を渡した場合は先頭4桁を年として使用)
pairYes
typeYes
viewNofull
limitNoデフォルト 200。1〜10000 の整数。type により実上限が変わる: 1min〜1hour は最大 10000(複数日取得)、4hour〜1month は最大 5000(複数年取得)、それ以外は 1000。実上限を超えると user エラー。
Behavior5/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 discloses key behavioral traits: how date and limit interact (returning candles before the end of the specified day in the given timezone), timezone handling with fallback to Asia/Tokyo, and dynamic maximum limits based on the candle type. This is thorough and transparent.

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?

The description is concise: a single paragraph covering the core functionality, followed by an important note about backtesting. Every sentence provides value, with no redundancy. It front-loads the purpose and references the schema for details, making it efficient.

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?

The description covers core functionality, parameter usage, timezone handling, and differentiation from backtesting. However, it lacks information about the output format (no output schema exists) and does not mention error conditions or authentication. For a data retrieval tool with 6 parameters and no output schema, this is a noticeable gap.

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 50% (only tz, date, limit have descriptions in the schema). The description text adds some high-level context about date interpretation and backtesting but does not significantly enhance understanding of the undocumented parameters (pair, type, view). The baseline for 50% coverage is 3, and the description does not sufficiently compensate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it retrieves OHLCV/candle data for various timeframes, using the verb '取得' and specifying the resource 'ローソク足'. It distinguishes itself from sibling tools like run_backtest by noting that backtesting should use that tool instead. The purpose is specific and unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly advises using run_backtest for backtesting instead of get_candles, providing a clear when-not-to-use case. It also explains date interpretation and limit behavior. However, it does not mention alternatives among sibling data retrieval tools like get_ticker or get_orderbook, leaving some gaps in guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/tjackiet/bitbank-lab-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server