Skip to main content
Glama
dzintars2

candlestick-chart-mcp

by dzintars2

Render candlestick chart

render_candlestick_chart
Read-onlyIdempotent

Turn OHLCV data into candlestick, Heikin-Ashi, or OHLC-bar charts. Returns PNG images with optional volume, overlays, and buy/sell markers.

Instructions

Draw a candlestick (or Heikin-Ashi / OHLC-bar) chart from OHLCV data and return it as a PNG image. Supports a volume panel, moving-average and Bollinger overlays, VWAP, log price scale, horizontal reference lines, buy/sell markers, and light/dark themes. Colours default to a colourblind-safe blue-up / red-down pair; pass colorScheme:"classic" for traditional green/red. No network calls are made.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emaNoExponential moving average periods.
smaNoSimple moving average periods.
vwapNoSession-anchored VWAP (needs volume on every bar).
scaleNoDevice-pixel ratio. Raise for print; 1 keeps the returned image small.
themeNodark
titleNoHeadline, e.g. "BTCUSD · 1h". Omit for a bare plot.
widthNoLogical width in px.
heightNoLogical height in px.
yScaleNoUse log for multi-year or high-growth ranges.linear
candlesYesOHLCV bars, oldest first (any order is accepted and sorted). Two accepted forms per bar: {"time":…,"open":…,"high":…,"low":…,"close":…,"volume":…} or the compact tuple [time, open, high, low, close, volume?]. Prefer the tuple form for long series — it costs far fewer tokens.
markersNoTriangular annotations: buy below the bar, sell above it.
showGridNo
subtitleNoSecond header line. Defaults to the date range, bar count and last close.
timeZoneNoIANA time zone used for every axis and header label.UTC
bodyStyleNoOverride body fill. Defaults to filled for diverging, hollow-up for classic and mono.
bollingerNoBollinger band overlay.
chartTypeNocandlestick = classic bodies; heikin-ashi = smoothed bodies; ohlc-bars = Western bar chart.candlestick
priceLinesNoHorizontal reference lines — support, resistance, entry, stop.
showLegendNo
showVolumeNoVolume panel below the price panel (needs a volume column).
colorSchemeNodiverging = blue up / red down (validated colourblind-safe, the default). classic = green up / red down (traditional but not CVD-safe, so up bodies are drawn hollow). mono = ink only, direction by hollow vs filled.diverging
showLastPriceNoDashed line plus axis chip at the final close.
Behavior4/5

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

The description discloses important behavioral traits: it returns a PNG image and makes no network calls. This goes beyond the existing readOnly and idempotent annotations, and does not contradict them. The color scheme default and override hint also add transparency.

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

Conciseness5/5

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

The description is three concise sentences, front-loaded with the core purpose. Every sentence adds value—drawing, features, and network behavior—without unnecessary fluff or repetition of schema details.

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?

Given the tool's complexity (22 parameters, nested objects) and absence of an output schema, the description covers the essential context: return type (PNG) and network behavior. However, it does not specify whether the PNG is returned as base64, a URL, or raw bytes, which is a minor gap for a tool with no output schema.

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

Parameters4/5

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

The schema already covers 86% of parameters in detail, so a baseline of 3 applies. The description adds a high-level feature overview (volume panel, moving averages, Bollinger, VWAP, etc.) that maps to parameters, and specifically advises on the 'classic' color scheme, which provides useful guidance beyond 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 clearly states the tool draws candlestick charts (with Heikin-Ashi and OHLC-bar variants) from OHLCV data and returns a PNG. It enumerates supported features, leaving no ambiguity about the tool's purpose.

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?

The description provides clear context on what the tool does and that it makes no network calls, but it does not explicitly state when to use it over alternatives. Since no sibling tools are listed, this is acceptable, yet explicit usage guidance is missing.

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/dzintars2/candlestick-chart-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server