Skip to main content
Glama
bitbank-lab-mcp

bitbank-lab-mcp

Official
by bitbankinc

analyze_indicators

Calculate technical indicators such as RSI, MACD, and SMA for a chosen crypto pair and timeframe, then return current values, trend signals, and plain-text analysis to support trading decisions.

Instructions

[Technical Indicators / RSI / MACD / SMA] テクニカル指標の総合分析。最新値・トレンド判定・シグナルをテキストで返す。十分な limit を指定(例: 日足200本)。

描画 → prepare_chart_data / render_chart_svg。バックテスト → run_backtest。

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "analyze_indicators"
  }
}

Input Schema

NameRequiredDescriptionDefault
tzNodate の暦日解釈と表示に使う IANA タイムゾーン(既定: Asia/Tokyo)。
dateNotype により形式が異なる: 1min/5min/15min/30min/1hour は YYYYMMDD、4hour/8hour/12hour/1day/1week/1month は YYYY(YYYYMMDD も先頭4桁として互換受理)。date は tz(既定 Asia/Tokyo)の暦日として解釈し、指定日の終端以前を対象にします。 指標計算に使う足を取得します。
pairNobtc_jpy
typeNo1day
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.6.0
    • addedInput schema / properties / date
      Added value: +{
      +  "description": "type により形式が異なる: 1min/5min/15min/30min/1hour は YYYYMMDD、4hour/8hour/12hour/1day/1week/1month は YYYY(YYYYMMDD も先頭4桁として互換受理)。date は tz(既定 Asia/Tokyo)の暦日として解釈し、指定日の終端以前を対象にします。 指標計算に使う足を取得します。",
      +  "type": "string"
      +}
    • addedInput schema / properties / tz
      Added value: +{
      +  "description": "date の暦日解釈と表示に使う IANA タイムゾーン(既定: Asia/Tokyo)。",
      +  "type": "string"
      +}
  2. Changed1 schema field changedv0.4.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. First observedv0.1.1

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses that results come back as text containing latest values, a trend determination, and signals, which is genuinely useful. It says nothing about which indicators are computed, any permissions or rate limits, or whether the analysis is deterministic across calls.

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?

The text is short and front-loaded: purpose first, then output form, then the limit hint, then routing to siblings. Each sentence carries information. The bracketed tag prefix duplicates some of what the first sentence already says, which is minor redundancy.

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?

With five optional parameters, no annotations, and no output schema, the description has to explain both inputs and returns. It sketches the return shape (latest values, trend, signals as text) and gives useful limit guidance, but leaves the timeframe and pair semantics and the exact set of computed indicators unspecified, so an agent still has to infer a good deal.

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 coverage is 40%; date and tz are well documented in the schema itself, but pair and type have no description. The description adds real guidance for limit by recommending a sufficient value with the concrete example of 200 daily bars, which the schema does not provide. It still leaves pair (default btc_jpy) and the timeframe enum unexplained, so compensation for the coverage gap is only partial.

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 description states a specific verb and resource: comprehensive analysis of technical indicators, returning the latest values, trend judgement, and signals as text. The bracketed tags (RSI/MACD/SMA) clarify which indicators are involved, which helps distinguish it from single-indicator siblings. However, it never explains how it relates to the numerous snapshot siblings such as analyze_sma_snapshot, analyze_ema_snapshot, or detect_macd_cross, so the differentiation is only partial.

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?

It explicitly routes two related workflows: use prepare_chart_data or render_chart_svg for drawing, and run_backtest for backtesting. It also gives the practical instruction to supply a sufficient limit (e.g. 200 daily bars). What is missing is guidance on when to prefer this tool over the individual indicator snapshot tools, and there are no explicit when-not-to-use conditions.

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