Skip to main content
Glama
tossinvest-mcp

tossinvest-mcp

by scjang01

시장 지표 캔들 차트 조회

toss_get_market_indicator_candles
Read-only

Retrieve OHLCV candles for Korean market indices and government bonds, newest first; indices support 1-minute or daily intervals, while bonds provide daily candles only.

Instructions

국내 지수·국채 OHLCV, 최신순. 지수만 분봉 지원; 국채는 일봉만. count 기본 20, 최대 200; 첫 호출에 필요한 봉 수 지정. nextBefore를 시간대 포함 ISO 8601 값 그대로 before에 전달.

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>",
      "interval": "<interval>"
    },
    "name": "toss_get_market_indicator_candles"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
beforeNo
symbolYes
intervalYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.2
    • removedInput schema / properties / before / pattern
      Removed 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)))$"
  2. Addedv0.3.0

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), and the description adds genuinely useful behavior: newest-first ordering, the default and maximum for count, and that a nextBefore value must be passed through unchanged as before. It stops short of explaining the response shape or what happens when before is omitted or invalid on the first call.

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?

Four compact clauses, each carrying a distinct constraint, delivered up front with no filler. The phrase about specifying the needed candle count on the first call is slightly redundant with the count default statement but still adds intent.

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?

For a four-parameter read tool with no output schema, the definition covers the resource domain, ordering, limits, interval legality, and the pagination cursor convention. Remaining gaps are small: no example symbol values, no clarification of the initial-call behavior for before, and only an indirect hint that nextBefore comes from the response.

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 description coverage is 0%, so the description has to carry the params and it largely does: count (default 20, max 200), before (ISO 8601 with timezone, copied verbatim from nextBefore), and interval applicability rules per symbol type. The symbol parameter is only characterized by domain (domestic index/bond) and its format is left entirely to the schema pattern.

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?

The description states a specific resource and scope: domestic index and government-bond OHLCV candles, returned newest-first. That scope implicitly separates it from the general candle siblings, but no sibling is named, so an agent must infer that stock candles belong to toss_get_candles rather than this tool.

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?

It gives concrete selection guidance for the interval parameter: minute candles are valid only for indices, while bonds are daily only, which prevents a whole class of invalid calls. It also explains the first-call versus follow-up call pattern for pagination, but never names an alternative tool or states when this should be skipped.

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