Skip to main content
Glama
shigechika

jquants-mcp

by shigechika

get_candlestick_data

Read-onlyIdempotent

Retrieve Japanese stock candlestick OHLCV data with indicators for charting. Supports adjustable date range and overlays like moving averages.

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?

Description adds value beyond annotations by explaining cache-only behavior, plan limitations, and the return structure. Annotations already declare read-only and idempotent, but description elaborates on caching and no API call. No contradictions.

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 sections and bullet points. Front-loaded with purpose. Slightly long but justified given the detail needed (no output schema). Could be slightly more concise but efficient overall.

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 tool complexity (5 parameters, no output schema), the description is very complete. Covers return structure, error handling, plan support, caching, and sibling tool reference. No gaps identified.

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?

With 0% schema coverage, the description provides thorough parameter explanations: code with example, date formats and defaults, indicators list with options, and adjusted with default. Fully compensates 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?

Description clearly states it returns candlestick OHLCV + indicator data as JSON. It specifies the resource (candlestick data) and the verb (return). Explicitly distinguishes from sibling get_comparison_chart_data for multi-stock comparison.

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?

Explicitly states when to use: for ローソク足・株価チャート・React artifact queries (JSON format). Provides alternative: 'For multi-stock comparison use sibling get_comparison_chart_data.' Also mentions supported plans and cache-only nature.

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