Skip to main content
Glama
bitbank-lab-mcp

bitbank-lab-mcp

Official
by bitbankinc

analyze_mtf_sma

Analyze SMA alignment and confluence across multiple timeframes for a crypto pair to determine trend direction and signal agreement.

Instructions

[Multi-Timeframe SMA / MTF] 複数タイムフレームSMA一括分析(multi-timeframe / MTF / SMA alignment / confluence)。整列方向とコンフルエンスを判定。

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

Input Schema

NameRequiredDescriptionDefault
pairNobtc_jpy
periodsNo
timeframesNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.7.0
    • addedInput schema / properties / periods / items / exclusiveMinimum
      Added value: +0
    • changedInput schema / properties / periods / items / maximum
      Previous value: -9007199254740991New value: +365
    • removedInput schema / properties / periods / items / minimum
      Removed value: --9007199254740991
  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

C2.6/5.0
Behavior2/5

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

With no annotations supplied, the description carries the full behavioral burden and discloses very little. It implies a read-only computation from the analysis framing and hints at output content ('alignment direction and confluence'), but says nothing about whether data is fetched live, caching, rate limits, or what the result looks like.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Very short and front-loaded, but a large share of the text is redundant keyword stuffing ('multi-timeframe / MTF / SMA alignment / confluence') that repeats the same concept four ways rather than adding information. Size is fine; density of value is low.

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?

For a three-parameter analytical tool with no annotations and no output schema, the description does not say enough — result shape, what 'confluence' concretely means, and parameter behavior are all left to the schema and guesswork.

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% across three parameters (pair, periods, timeframes), so the description must compensate and only partly does: '複数タイムフレームSMA' conveys that timeframes and SMA periods are inputs, but it does not explain the pair argument, the meaning/constraints of the periods array, or allowed timeframe granularity.

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 a specific verb and resource — batch SMA analysis across multiple timeframes — plus its output focus ('整列方向とコンフルエンスを判定', i.e. alignment direction and confluence). It is clear what the tool computes, but it never distinguishes itself from nearby siblings such as analyze_sma_snapshot or analyze_indicators.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No when-to-use, when-not-to-use, or alternative is stated. An agent must infer that 'MTF' in the name means this is the tool for multi-timeframe alignment rather than a single-timeframe SMA snapshot; nothing in the text routes it.

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