Skip to main content
Glama
shigechika

jquants-mcp

by shigechika

get_derivatives_bars_daily_options

Read-onlyIdempotent

Retrieve daily OHLC, volume, open interest, and implied volatility for Japanese options (Nikkei 225, TOPIX). Filter by category, code, and contract month.

Instructions

Daily options OHLC bars with IV (オプション日足). Premium only.

Use for オプション, 日経オプション, TOPIXオプション, IV, implied volatility, オプション建玉. Returns OHLC, volume, open interest, and implied volatility. For Nikkei 225 options only (Standard+), use get_derivatives_bars_daily_options_225.

[Supported plans] Premium

Args: date: Date (YYYYMMDD or YYYY-MM-DD) (required) category: Product category (e.g. Options225 (日経225オプション), OptionsTOPIX (TOPIXオプション)). Omit for all categories. code: Issue code contract_flag: Contract month flag (0 = all, 1 = front month, 2 = back month)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dateYes
categoryNo
codeNo
contract_flagNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Behavior4/5

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

Annotations already declare safe read-only behavior. Description adds return fields (OHLC, volume, OI, IV) and plan restriction (Premium). 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?

Description is concise and front-loaded with key info. Minor repetition of 'Premium' in both description and plan line, but overall efficient.

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?

Complex tool with 4 parameters and output schema present. Description covers parameter meanings, return types, and sibling differentiation. Sufficient given annotations and 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?

Schema coverage is 0%, but description compensates by explaining each parameter with format examples and valid values (e.g., contract_flag options). Adequate for parameter understanding.

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 'Daily options OHLC bars with IV' and mentions specific resources (オプション, 日経オプション, TOPIXオプション). It also distinguishes from sibling tool for Nikkei 225 options.

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?

Provides clear usage context (options, IV, etc.) and explicitly names alternative tool for Nikkei 225 options only. However, no general when-not-to-use guidance.

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