toss_get_candlesFetch 1-minute or daily OHLCV candles for a KRX or US stock symbol to analyze price and volume history. Specify symbol and interval; optionally set count, before time, and adjusted prices.
Get 1-minute or daily OHLCV candles for one KRX or US stock symbol.
| Name | Required | Description | Default |
|---|---|---|---|
| count | No | ||
| before | No | ||
| symbol | Yes | ||
| adjusted | No | ||
| interval | Yes |
Changes observed during successful MCP inspections.
v0.3.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / before / patternPrevious value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z|([+-](?:[01]\\d|2[0-3]):[0-5]\\d)))$"v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the interval granularity and the KRX/US scope, but says nothing about the 200-candle cap, how 'before' paginates, default ordering, or timezone/date semantics of the returned candles.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single front-loaded sentence with no filler; the scope qualifiers (interval options, single symbol, market coverage) are packed efficiently with zero redundancy.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema, so the description should at least sketch the OHLCV return shape, but it does not. Combined with zero-coverage parameters and no pagination or adjustment notes, an agent has to guess at how to page history and what 'adjusted' changes.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, so the description must carry parameter meaning, yet it only explains symbol and interval. The three remaining parameters — count (1–200), before (ISO date-time cursor) and adjusted (split/dividend adjustment) — are entirely undocumented anywhere, and 'adjusted' in particular is ambiguous without explanation.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb (Get), a specific resource (OHLCV candles), the supported granularities (1-minute or daily) and the symbol universe (one KRX or US stock symbol). This also implicitly separates it from toss_get_market_indicator_candles, which handles indicators rather than individual stock symbols.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is only implied by the verb and resource — an agent can infer this is the tool for charting a single symbol. There is no explicit guidance on when to prefer it over toss_get_prices or toss_get_market_indicator_candles, and no mention of prerequisites or pagination workflow.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.