Skip to main content
Glama
bitbankinc

bitbank-lab-mcp

Official
by bitbankinc

analyze_stoch_snapshot

Analyze current Stochastic oscillator to detect overbought/oversold zones, crossovers, and divergences for potential trend reversals.

Instructions

[Stochastic / Overbought / Oversold] Stochastic(stochastic / %K / %D / overbought / oversold / divergence)の最新状態。ゾーン・クロス・ダイバージェンスを判定。

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pairNobtc_jpy
typeNo1day
limitNo
kPeriodNo
smoothDNo
smoothKNo
Behavior3/5

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

No annotations provided, so description must carry burden. It states it returns 'latest status' and 'determines zone, cross, divergence', which implies a read-only analysis. However, it does not explicitly confirm no side effects or clarify any behavioral traits beyond the analysis type, leaving some ambiguity.

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?

Description is short (3 sentences) and front-loaded with the indicator name. Includes a warning and a clear alternative tool reference. Could be slightly more concise by removing redundant symbols, but overall efficient.

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

Completeness2/5

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

Even for a simple snapshot tool without output schema, the description fails to specify the return format or what exactly each determination (zone, cross, divergence) looks like. With 6 parameters and no explanation, the agent lacks sufficient context for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, yet the description does not explain any of the 6 parameters (pair, type, limit, kPeriod, smoothD, smoothK). It only mentions stochastic terms like %K and %D but not how parameters affect calculation. This provides minimal added value over the 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 states 'Stochastic / Overbought / Oversold' and specifies it analyzes 'zone, cross, divergence'. It clearly distinguishes from sibling tools like 'analyze_bb_snapshot' by naming the specific indicator. The verb 'analyze' and resource 'stochastic snapshot' are explicit.

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?

Provides explicit guidance: 'Only latest value' and directs users to 'prepare_chart_data (indicators: ["STOCH"])' for time series. This tells when not to use the tool. Missing comparison with other analyze_* siblings but the indicator-specific naming implies use for stochastic analysis.

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