Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by clauzewitz

get_market_indicator_candles

Read-onlyIdempotent

Retrieve OHLC candlestick data for Korean market indices and government bonds, including KOSPI, KOSDAQ, and KR bond tenors, with 1-minute or daily intervals and pagination for historical analysis.

Instructions

국내 지수·국채의 캔들(OHLC)을 최신순으로 조회한다 (최대 200개).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "symbol": "<symbol>"
    },
    "name": "get_market_indicator_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo봉 개수 (최대 200)
beforeNo이 시각(ISO 8601, 포함) 이전 봉만 조회. 다음 페이지는 이전 응답의 nextBefore 값을 넣는다
symbolYes
intervalNo1m 분봉(KOSPI·KOSDAQ 만), 1d 일봉1d

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so safety is covered by structured data. The description adds two useful behavioral facts: results are newest-first and capped at 200. It says nothing about pagination continuation, latency, or rate limits, so it clears but does not exceed the lower bar set by 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?

A single front-loaded sentence with no wasted words; the ordering and cap are packed into the parenthetical. It is efficient but so terse that the agent gains no routing or pagination context, leaving the sentence slightly thin rather than tight.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

A read-only listing tool with no output schema and annotations carrying the safety profile, so the description does not need to explain return values. However, with four parameters and cursor-based paging available, omitting any mention of how to paginate (using nextBefore) leaves an operational gap.

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

Parameters3/5

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

Schema description coverage is 75%, with `before`/nextBefore and the interval restrictions documented in-schema. The description only restates the 200 cap (already in the `count` schema) and the ordering; it adds no meaning beyond the schema for symbol, interval, or cursor semantics, so baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: retrieves OHLC candles for domestic indices and government bonds, ordered newest-first with a 200 cap. The '지수·국채' scope implicitly separates it from get_candles (individual stock candles) and get_market_indicator_prices, but no sibling is ever named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied by the asset-class scope ('국내 지수·국채'), which lets an agent infer it should prefer get_candles for stocks. There is no explicit when/when-not guidance, no mention of get_market_indicator_prices as the non-candle alternative, and no hint about the 1m interval being restricted to KOSPI/KOSDAQ.

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