bitflyer-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tickerA | bitFlyer の最新ティッカーを取得する (read-only)。 返す主な値: ltp (最終取引価格), best_bid / best_ask (最良気配), volume (出来高), timestamp。 product_code 例: FX_BTC_JPY (BTC証拠金FX), BTC_JPY (現物), ETH_JPY, XRP_JPY。 |
| get_boardA | bitFlyer の板情報 (オーダーブック) を上位 depth 段に要約して取得する (read-only)。 返す値: mid_price, spread, best_bid, best_ask, 上位 depth 段の bids/asks。 全板は数百〜千件あるため depth (既定10) 段に圧縮して返す。 product_code 例: FX_BTC_JPY, BTC_JPY。 |
| get_executionsA | 直近の約定履歴 (recent trades) を取得する (read-only)。 各約定: price, size, side (BUY/SELL), exec_date。count は 1〜100 (既定20)。 |
| get_board_stateB | 板の状態 (health, state, 特別気配 SFD など) を取得する (read-only)。 state 例: RUNNING (通常), CLOSED, STARTING, PREOPEN, CIRCUIT BREAK。 取引可能かの判断に使える。 |
| get_healthC | 取引所の稼働状況を取得する (read-only)。 status 例: NORMAL, BUSY, VERY BUSY, SUPER BUSY, NO ORDER, STOP。 |
| list_marketsA | bitFlyer で取引可能な全 product (現物・FX・先物) の一覧を取得する (read-only)。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool targets a distinct piece of data: order book summary, board state, recent trades, exchange health, ticker, and market list. No overlap in purpose.
All tools follow a consistent verb_noun snake_case pattern, using 'get_' for most and 'list_' for one, which is a standard alternative.
6 tools is appropriate for a read-only market data server, covering essential endpoints without unnecessary clutter.
The set covers core market data: order book, trades, ticker, exchange status, and available markets. No obvious gaps for typical data retrieval needs.