Skip to main content
Glama
bitbankinc

bitbank-lab-mcp

Official
by bitbankinc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

render_candle_pattern_diagram

Visualize candlestick pattern analysis results as an educational diagram, highlighting the confirmed candles to clarify chart pattern structure for beginners.

Instructions

[Candle Pattern Diagram / Education] ローソク足パターンの教育用構造図（candle pattern diagram / education / visualization）。analyze_candle_patterns の結果を初心者向けに視覚化。

ユーザーが「図で見せて」等と明示した場合のみ使用。自発的呼び出し禁止。data.svg を受け取ったら Visualizer(show_widget) の widget_code にそのまま渡してレンダリングすること。 チャット本文へのSVGコード直接出力は禁止。

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
themeNodark
titleNoChart title (default: pattern name or "ローソク足チャート")
candlesYesCandle data array (oldest first)
patternNoPattern to highlight

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.5.0
    • addedInput schema / properties / pattern / properties / involvedIndices / items
      Added value: +false
    • addedInput schema / properties / pattern / properties / involvedIndices / maxItems
      Added value: +2
    • addedInput schema / properties / pattern / properties / involvedIndices / minItems
      Added value: +2
  2. Changed3 schema fields 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"
    • removedInput schema / properties / pattern / properties / involvedIndices / items
      Removed value: -[
-  {
-    "maximum": 9007199254740991,
-    "minimum": 0,
-    "type": "integer"
-  },
-  {
-    "maximum": 9007199254740991,
-    "minimum": 0,
-    "type": "integer"
-  }
-]
    • addedInput schema / properties / pattern / properties / involvedIndices / prefixItems
      Added value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  },
+  {
+    "maximum": 9007199254740991,
+    "minimum": 0,
+    "type": "integer"
+  }
+]
  3. First observedv0.1.1

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the disclosure burden. It discloses that this is an educational visualization, that the SVG must be passed to show_widget, and that direct SVG output to chat is forbidden. It does not state return shape explicitly, but data.svg is referenced.

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?

The content is front-loaded and compact, but the bracketed tags repeat the Japanese phrase ('Candle Pattern Diagram / Education' vs 'candle pattern diagram / education / visualization'), adding clutter. Still, every substantive sentence earns its place.

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

Completeness4/5

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

For a 4-parameter rendering tool with no output schema, the description covers the essential context: when to invoke, what data it visualizes, and how to render the returned SVG. Minor gaps like exact output format are partially addressed by the data.svg/Visualizer note.

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 75%, so the schema already documents title, candles, pattern, and nested fields. The description adds no parameter-specific meaning beyond mentioning analyze_candle_patterns results, so it provides only baseline value.

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 a specific verb (visualize/render) and resource (educational candlestick pattern diagram), and ties it to analyze_candle_patterns results for beginners. This distinguishes it from sibling renderers like render_chart_svg and render_depth_svg by naming its upstream analysis tool and educational intent.

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 says to use only when the user asks for a diagram and forbids spontaneous calls, and it explains that the result must go through Visualizer(show_widget). It does not explicitly name a sibling alternative, but the analyze_candle_patterns dependency makes the context clear.

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

Deploy Server

Other Tools