Skip to main content
Glama
bitbankinc

bitbank-lab-mcp

Official
by bitbankinc

prepare_chart_data

Fetch candlestick (OHLCV) chart data with optional technical indicators for cryptocurrency pairs. Customize timeframe, limit, and timezone for localized timestamps.

Instructions

[Chart / Candlestick / Visualization] チャート描画の第一選択ツール。

⚠️ limit はデフォルト 30 を推奨。ユーザーが期間を明示した場合のみ増やすこと。 indicators はユーザーが明示的に要求した指標のみ指定すること。分析のついでに追加しない。 indicators の同時指定はコンテキストを大幅に消費するため、必要最小限に留めること。

デフォルトはローソク足(OHLCV)のみ返す。indicators 未指定 = ローソク足のみ。 指標が必要な場合は indicators に明示指定: SMA_5, SMA_20, SMA_25, SMA_50, SMA_75, SMA_200, EMA_12, EMA_26, EMA_50, EMA_200, BB, ICHIMOKU, RSI, MACD, STOCH

レスポンス形式: { times[], labels?[], candles: [[o,h,l,c,v],...], series?: {指標名: values[]}, subPanels?: {...} } JPY ペアの価格は整数に丸め済み。全 null 系列は自動除外。

tz パラメータ(例: "Asia/Tokyo")指定時、times がローカル時刻に変換され、labels("03/16 17:00" 等の短縮表示文字列)も付加される。

SVG/PNG ファイル保存 → render_chart_svg。指標の最新値やトレンド判定 → analyze_indicators。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
tzNoタイムゾーン(デフォルト: Asia/Tokyo)。times をローカル時刻に変換し、labels(短縮表示文字列)も付加する。空文字でUTCのみAsia/Tokyo
pairNobtc_jpy
typeNo1day
limitNo
indicatorsNo
Behavior4/5

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

No annotations present, so description carries full burden. It discloses response format, rounding behavior for JPY pairs, automatic exclusion of null series, timezone effects, and context consumption by indicators. Lacks rate limits or auth requirements but is thorough for a data retrieval tool.

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?

Well-structured with bullet points and emojis, front-loading purpose. Slightly lengthy but each sentence adds value; no redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 5 parameters, no output schema, and complexity (indicators, timezone, response format), description covers response format, special behaviors, and sibling tools. Missing output structure for subPanels/series details, but sufficient for agent use.

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 low (20%), but description compensates by explaining tz parameter behavior, default limit recommendation, indicators list with usage note, and default output. Could detail pair format and type options more, but adds significant value beyond schema.

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 is the first choice for chart drawing, returning OHLCV candlesticks and optionally indicators. It distinguishes from siblings like render_chart_svg and analyze_indicators by specifying their roles.

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

Usage Guidelines5/5

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

Explicit guidelines provided: limit default 30 recommended, only increase if user specifies period; indicators only when explicitly requested; alternatives noted (SVG/PNG → render_chart_svg, indicator analysis → analyze_indicators).

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/bitbankinc/bitbank-lab-mcp'

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