Skip to main content
Glama
tjackiet

bitbank-mcp-server

by tjackiet

prepare_depth_data

Retrieves order book depth data as cumulative volume arrays for bids and asks, including best prices, spread, and mid-based band analysis for market visualization.

Instructions

[Depth Chart / Order Book / Visualization] 板の深度チャート描画の第一選択ツール。

getDepth(/depth API)を呼び出し、累積 volume の階段配列 ([price, cumulativeVolume][]) として返す。 Claude.ai の Visualizer 等クライアント側で描画可能な場合はこのツールを優先。 ファイル保存(SVG/PNG)が必要な場合は render_depth_svg を使用。

レスポンス形式: { bids: [[price, cumVolume], ...], asks: [[price, cumVolume], ...], bestBid, bestAsk, mid, spread, spreadPct, totalBidVolume, totalAskVolume, band: {pct, bidVolume, askVolume, ratio}, timestamp, isoTime }

  • bids は価格降順、asks は価格昇順

  • band は mid を中心とした ±bandPct 範囲の買い/売り量と比率(ratio = bidVolume / askVolume)

  • JPY ペアの価格は整数に丸め済み

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairNobtc_jpy
levelsNo取得する最大レベル数(片側)。10〜1000 の整数、デフォルト 200
bandPctNomid を中心とした ±range 比率。0.01 = ±1%。デフォルト 0.01
Behavior4/5

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

No annotations, so description carries full burden. It details return format, bid/ask ordering, band calculation, and JPY rounding. Lacks auth/rate limit info but sufficient for behavioral understanding.

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?

Front-loaded with purpose, each sentence adds value. Slightly long but well-structured.

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?

Thorough description of return data, ordering, and band calculation. No output schema, but covers essential details. Could mention error handling.

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 67%. Description adds context for bandPct (mid ± range) and explains levels default, but pair lacks description. Adds some 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?

Explicitly states it is the first-choice tool for depth chart visualization, calls getDepth API, and returns cumulative volume array. Clearly distinguishes from render_depth_svg.

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?

States when to use (visualizer capable) and when to use alternative render_depth_svg (file saving). But does not mention other alternatives like get_orderbook.

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