Skip to main content
Glama
INo-xious

stockbit-mcp

by INo-xious
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

price_chart

Read-only

Renders an SVG candlestick chart for IDX stocks with volume, technical overlays, RSI/MACD panels, and support/resistance levels. Draw custom trend lines and markers to support your analysis.

Instructions

Candlestick chart for an IDX stock, ALWAYS rendered as an SVG: daily candles with volume, optional overlays (SMA/EMA/Bollinger) and sub-panels (RSI, MACD), plus support/resistance levels drawn on. Returns the image AND writes a .svg, reporting the path in savedTo. Use technicals for the numbers; this is the picture. annotations draws your own levels, zones, trend lines and markers, which is how you show the evidence behind an analysis. Drawing happens on this render only — nothing is written to the Stockbit account. The result counts yours and this tool's apart. autoLevels is the support/resistance this tool detected itself (show_levels, on by default); annotationsDrawn counts YOUR annotations by kind — level, zone, trend, marker — so you can confirm each one landed. annotationsNotDrawn names the ones that did not, by their index in your array and why: a date outside the plotted window, or a kind that arrived without the fields it needs. It is never silently empty about something that was skipped. Whenever this draws, it also opens the symbol's Stockbit chart in the user's own default browser so they can compare the drawing against the live chart in their own session. stockbitUrl in the result is that page; pass open_in_stockbit: false to skip opening it.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNoLatest session, YYYY-MM-DD
barsNoSessions to plot (default 120)
fromNoEarliest session, YYYY-MM-DD
themeNoDefault dark
panelsNoSub-panels below price. Default rsi.
symbolYesIDX ticker, e.g. BBRI
browserNoBrowser to open Stockbit in, by name, e.g. "Edge". Defaults to STOCKBIT_WEB_BROWSER, else the OS default.
overlaysNoPrice overlays. Default sma20 + sma50.
save_pathNoWhere to write the .svg. Defaults to charts/ inside the store (~/.stockbit, or $STOCKBIT_STORE_DIR).
annotationsNoYour own drawings on top of the chart. Same shape chartbit_draw takes.
show_levelsNoDraw support/resistance from pivot clustering. Default true.
show_volumeNoDefault true
open_in_stockbitNoOpen the symbol's Stockbit chart in the user's browser. Default true.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv1.3.0
    • changedInput schema / properties / annotations / description
      Previous value: -"Your own drawings on top of the chart"New value: +"Your own drawings on top of the chart. Same shape chartbit_draw takes."
    • addedInput schema / properties / annotations / items / properties / fromDate
      Added value: +{
+  "description": "Alias for `from_date`.",
+  "type": "string"
+}
    • addedInput schema / properties / annotations / items / properties / fromPrice
      Added value: +{
+  "description": "Alias for `from_price`.",
+  "type": "number"
+}
    • addedInput schema / properties / annotations / items / properties / toDate
      Added value: +{
+  "description": "Alias for `to_date`.",
+  "type": "string"
+}
    • addedInput schema / properties / annotations / items / properties / toPrice
      Added value: +{
+  "description": "Alias for `to_price`.",
+  "type": "number"
+}
  2. Addedv1.2.2

TDQS

A4.8/5.0
Behavior5/5

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

Annotations provide readOnlyHint, openWorldHint, and destructiveHint, and the description adds substantial beyond-annotation context: the tool always writes a .svg and reports savedTo, opens a browser by default, draws only on this render without writing to the Stockbit account, and reports annotationsDrawn/annotationsNotDrawn rather than silently dropping input. This is far more transparent than the annotations alone.

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?

The description is long but dense and front-loaded: purpose first, then usage routing, then side effects and result semantics. Every sentence conveys useful operational information, though a shorter version could integrate the annotation-counting explanation more tightly.

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

Completeness5/5

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

For a tool with 13 parameters and no output schema, the description covers the key missing context: SVG output, savedTo reporting, local file side effect, browser-opening behavior, auto-detected levels versus user annotations, and failure reporting. An agent has enough to call it correctly and interpret the result.

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?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying the roles of `annotations`, `show_levels`/`autoLevels`, and `open_in_stockbit`, and by explaining how annotation failures surface in the result. It does not redundantly re-list every property, so it earns above baseline.

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 opens with a precise verb and resource: 'Candlestick chart for an IDX stock, ALWAYS rendered as an SVG.' It clearly distinguishes itself from siblings by saying 'Use `technicals` for the numbers; this is the picture,' which lets an agent pick the right tool without inferring from schema.

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?

The description explicitly names the main alternative ('Use `technicals` for the numbers; this is the picture') and gives concrete guidance on when to use annotations for user-drawn evidence. It also explains the open_in_stockbit behavior so the agent can decide whether to suppress that side effect.

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