Skip to main content
Glama
shigechika

jquants-mcp

by shigechika

get_candlestick_data

Read-onlyIdempotent

Retrieve candlestick OHLCV and technical indicators for a Japanese stock as JSON, with parallel arrays for chart rendering.

Instructions

Return candlestick OHLCV + indicator data as JSON (ローソク足データJSON). All plans.

Use for ローソク足・株価チャート・React artifact チャート queries (JSON format). Returns parallel arrays for Plotly/Recharts React artifact rendering. For multi-stock comparison use sibling get_comparison_chart_data.

[Supported plans] Free / Light / Standard / Premium (cache-only, no API call)

Args: code: Stock code (e.g. "7203" or "72030"). from_date: Range start (YYYYMMDD or YYYY-MM-DD). Default: 91 days before to_date. to_date: Range end (YYYYMMDD or YYYY-MM-DD). Default: today. indicators: Overlays list. Default ["volume","sma5","sma25"]. Options: volume, sma5, sma20, sma25, sma60, sma75, sma200, bb20. adjusted: Use split-adjusted prices (default True).

Returns: dict with keys: code — normalised 5-char code display_code — 4-char display code (e.g. "7203") company — brief company name or null from_date — YYYY-MM-DD display start to_date — YYYY-MM-DD display end adjusted — bool dates — list[str] YYYY-MM-DD ohlcv — {open, high, low, close, volume} each list[float] indicators — {sma5, ..., bb20_upper, bb20_mid, bb20_lower} list[float|null] lock_days — list[{date, direction, price}] earnings_dates — list[str] YYYY-MM-DD within the display window On error: {"error": ""}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
codeYes
from_dateNo
to_dateNo
indicatorsNo
adjustedNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already indicate read-only, non-destructive, idempotent. Description adds value by stating 'cache-only, no API call' and covering all plans, providing extra behavioral context beyond annotations.

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?

Well-structured with clear sections: purpose, usage, plans, args, returns. Slightly verbose with repeated info (e.g., 'All plans' appears twice), but overall efficient and front-loaded with key purpose.

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?

Given the complex return type (multiple lists, nested indicators) and 5 parameters, the description fully details all return keys (code, dates, ohlcv, indicators, lock_days, earnings_dates) and error format. No gaps relative to tool complexity.

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

Parameters5/5

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

Schema description coverage is 0%, but the description thoroughly explains all 5 parameters: code format, from/to date formats and defaults, indicator options list, adjusted boolean default. This compensates fully for missing schema descriptions.

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 it returns candlestick OHLCV + indicator data as JSON. It specifies the resource and verb, and distinguishes from sibling get_comparison_chart_data by noting it's for single stock only.

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?

Explicit guidance on when to use (candlestick, chart queries) and when not (multi-stock comparison, directing to sibling). Also mentions supported plans and cache-only behavior.

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/shigechika/jquants-mcp'

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