tossinvest-mcp

Get index or bond yield candles

tossinvest_get_market_indicator_candles

Read-onlyIdempotent

Fetch OHLCV candles for Korean indices and treasury yields, newest first. Pick symbol and interval (1m for indices, 1d for yields), request up to 200 bars, and page backward with nextBefore.

Instructions

Get OHLCV history for a Korean index or treasury yield, newest bar first. Max 200 bars per call.

Args:

symbol: one of KOSPI, KOSDAQ, KR_BOND_2Y, KR_BOND_3Y, KR_BOND_5Y, KR_BOND_10Y, KR_BOND_20Y, KR_BOND_30Y.
interval ('1m' | '1d'): '1m' is supported for KOSPI and KOSDAQ ONLY. KR_BOND_* support '1d' only and reject '1m' with 400 invalid-request.
count (number): 1-200, default 100.
before (string, optional): ISO 8601 inclusive upper bound. Pass the previous response's nextBefore to page backwards.
response_format ('markdown' | 'json'): default 'markdown'.

Returns { symbol, interval, count, candles: [{ timestamp, openPrice, highPrice, lowPrice, closePrice, volume }], nextBefore }. For KR_BOND_* the OHLC values are yields in percent, not prices.

Errors: 400 unsupported-symbol outside the catalog; 400 invalid-request for '1m' on a bond symbol.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`count`	No	Number of bars to return (max 200).
`before`	No	Inclusive upper bound (ISO 8601). Use the previous response's nextBefore to page backwards.
`symbol`	Yes	Market indicator symbol. Indices: KOSPI, KOSDAQ. Korean treasury yields: KR_BOND_2Y/3Y/5Y/10Y/20Y/30Y.
`interval`	Yes	'1d' for all symbols; '1m' only for KOSPI and KOSDAQ.
`response_format`	No	Output format: 'markdown' for a compact human-readable summary, 'json' for the complete raw payload.	markdown

Output Schema

TableJSON Schema

Name	Required	Description	Default
`count`	Yes
`symbol`	Yes
`candles`	Yes
`interval`	Yes
`truncated`	No
`nextBefore`	No
`truncation_message`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Sep 8, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Annotations already indicate read-only, idempotent, non-destructive behavior. The description adds valuable operational details such as error codes, unsupported intervals, and the fact that bond OHLC values are yields in percent. No contradiction with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-organized with Args, Returns, and Errors sections. It is compact, avoids fluff, and each line adds necessary information for correct usage.

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?

The description covers the return shape, error conditions, format options, and the special interpretation of bond yields. No important usage detail is missing for an agent to call this tool effectively.

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?

Input schema already covers all parameters with descriptions. The description adds meaningful extra guidance, especially the pagination mechanism via 'nextBefore' and the explicit restriction that '1m' is invalid for bond symbols.

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?

Clearly states it retrieves OHLCV history for Korean indices and treasury yields, distinguishing the resource and scope from other market data tools. The verb and target are specific and unambiguous.

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 including valid symbols, interval restrictions, max bar count, pagination behavior, and special bond yield semantics. Does not explicitly contrast with sibling tools, but the intended use case is well implied.

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

Deploy Server