Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

chart_series

Read-only

Fetch an IDX symbol's price chart series for a calendar window (1w to 5y) in one request, oldest first; fall back to paged bars tools on error.

Instructions

A chart price series for one symbol in ONE request, oldest observation first. This is the cheap path. The other one (the bars family) pages 12 rows at a time, so a year costs ~21 upstream calls and three years ~62; this costs one. Prefer it when you need a series and a calendar window is good enough. timeframe is a CALENDAR WINDOW, not a bar interval, and must be lowercase: 1w, 1m, 3m, ytd, 1y, 3y, 5y. Read granularity: 1w is intraday and preserves full Jakarta timestamps; longer windows are usually daily. An uppercase or interval-style value (1D, DAILY) is refused here rather than sent, because the server answers those with HTTP 200 and an empty series that looks exactly like a symbol with no history. This tool ERRORS instead of returning an empty series — including when the response parses but holds no points. An empty result would be indistinguishable from a broken fast path, so on an error fall back to the paged bars tools rather than concluding the symbol has no data. Check unmapped and warnings on the result before using the numbers. On the daily route the close arrives as value and open/high/low/volume arrive EMPTY, so every candle is flat and warnings says so: candlestick patterns and high/low indicators are meaningless on this series. Volume on that route comes back NULL, not 0 — a field that arrived empty on every bar is absent, and warnings names every such field. mapped, extraKeys and sample show which wire keys were used and what else the point carried. raw=true returns THIS ROUTE'S payload untouched instead of bars — the same request, with nothing projected. Use it only to discover real field spellings when unmapped or extraKeys is non-empty; it is not a fallback and returns no bars. raw=true used to read a DIFFERENT endpoint. It called /charts/:symbol while the projection reads /charts/:symbol/daily, and handed the first the second's vocabulary — so the escape hatch could not reproduce the payload it exists to diagnose. Measured 2026-09-01 the two do not share a vocabulary: /charts/:symbol REFUSES 1w with 400 "Kurun waktu tidak valid" and answers {chart_points: []} for everything else, while the daily route accepts 1w and answers the rich payload. That is why 1w errored and 1m came back empty — the route was wrong, not the value. Fixed: raw now reads the same route as the projection.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>",
      "timeframe": "<timeframe>"
    },
    "name": "chart_series"
  }
}

Input Schema

NameRequiredDescriptionDefault
rawNoReturn the unprojected chart payload instead of bars. Default false.
symbolYesIDX ticker, e.g. BBRI
timeframeYesCalendar window, lowercase: 1w, 1m, 3m, ytd, 1y, 3y, 5y. Read granularity to distinguish intraday points from daily bars.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile, and the description adds substantially: it errors rather than returning an empty series, the daily route delivers close as `value` with empty OHLC and NULL volume, `warnings` names every absent field, and `unmapped`/`extraKeys`/`sample` should be checked before trusting numbers. These are non-obvious traits that would otherwise cause silent misinterpretation.

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 core guidance is front-loaded well, but the final paragraph is a bug-history changelog ('Measured 2026-09-01 ...', 'Fixed: raw now reads the same route') whose diagnostic detail mostly does not change how an agent should call the tool. The repeated emphasis on the empty-series vs error distinction could be tightened.

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?

With no output schema, the description carries the burden of describing the return value and does so: it names the result fields (`bars`, `mapped`, `extraKeys`, `sample`, `unmapped`, `warnings`), the flat-candle condition on the daily route, and what raw=true returns instead. Nothing an agent needs to call this correctly and interpret the result is missing.

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, but the description goes further by stressing that `timeframe` is a calendar window rather than a bar interval and that an uppercase/interval value is refused client-side because the server would answer HTTP 200 with an empty series. `raw=true` is likewise explained as returning the unprojected payload with no `bars`. Only the exact granularity mapping per window stays vague ('usually daily').

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?

It states a specific verb and resource ('A chart price series for one symbol in ONE request, oldest observation first') and explicitly contrasts itself with the `bars` family by naming the cost difference (1 call vs ~21/62). An agent can distinguish this from `intraday_prices` or the paged bars tools without opening a 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?

It gives an explicit preference rule ('Prefer it when you need a series and a calendar window is good enough'), names the alternative family, and prescribes the fallback on error ('fall back to the paged bars tools rather than concluding the symbol has no data'). It also limits raw=true ('Use it only to discover real field spellings ... it is not a fallback'), which is exactly the when/when-not guidance an agent needs.

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