Skip to main content
Glama
bitbank-lab-mcp

bitbank-lab-mcp

Official
by bitbankinc

analyze_bb_snapshot

Analyze current Bollinger Bands snapshot values for a trading pair and timeframe; select default ±2σ or extended ±1σ/±2σ/±3σ modes to evaluate volatility and squeeze conditions.

Instructions

[Bollinger Bands / BB / Squeeze] ボリンジャーバンド(BB / squeeze / bandwidth / zScore)の数値スナップショット。軽量・BB特化。zScore は σ 単位(±2 が上下のバンド)。

mode=default: ±2σ帯の基本情報 / mode=extended: ±1σ/±2σ/±3σの詳細分析。

⚠️ 最新値のみ。時系列チャート描画 → prepare_chart_data(indicators: ["BB"])。

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_bb_snapshot"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNodefault
pairNobtc_jpy
typeNo1day
limitNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
  2. First observedv0.1.1

TDQS

A3.8/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 burden. It does disclose meaningful behavior — this returns only the most recent values (no history) and that zScore is expressed in σ units with ±2 as the bands — but it says nothing about cost, permissions, or what the returned snapshot fields look like beyond zScore.

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?

Dense but well structured: bracketed keyword tags, a one-line purpose, a mode map, then a warning plus alternative. The keyword stacking ('Bollinger Bands / BB / Squeeze') is mild redundancy that arguably aids search; nothing is wasted, though the message mixes two languages.

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 no annotations and no output schema, the description is the only source of behavioral detail, and it covers the latest-value constraint and zScore units but not the returned field set or the role of limit. Adequate to invoke, incomplete for interpreting the result.

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 0%, so the description must compensate. It does explain the semantic difference between the two mode enum values, which the schema only lists, but it says nothing about pair, type, or limit (min 40 / max 365, default 120) — an agent cannot tell what limit counts or how it interacts with a 'latest value only' snapshot. Partial compensation, so mid-range.

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 names the exact indicator family (Bollinger Bands / BB / squeeze / bandwidth / zScore) and characterizes the output as a numeric snapshot that is lightweight and BB-specialized, so an agent can tell it apart from the chart-drawing sibling it explicitly names. It does not, however, differentiate itself from the broader analyze_indicators or from the other analyze_*_snapshot siblings.

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?

It explicitly routes the agent: mode=default for basic ±2σ info, mode=extended for the full ±1σ/±2σ/±3σ breakdown, and a clear exclusion with an alternative — 'latest value only; for time-series chart drawing use prepare_chart_data (indicators: ["BB"])'. The when-to-use, when-not-to-use, and alternative are all stated.

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