Skip to main content
Glama
Sign In
kiwoom-mcp-server

kiwoom-mcp-server

by ChunSam
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

주식 차트 조회 (일/주/월/년/분/틱봉)

get_stock_chart

Fetch candlestick chart data for a stock code, supporting day, week, month, year, minute, and tick periods. Adjust count, minute scope, or tick scope to control chart detail.

Instructions

종목의 캔들 차트 데이터를 조회합니다 (키움 ka10079~ka10083/ka10094, 수정주가 반영). period: day(일봉, 기본)/week(주봉)/month(월봉)/year(년봉)/minute(분봉)/tick(틱봉). 분봉은 minute_scope로 분 단위를, 틱봉은 tick_scope로 캔들당 틱 수를 지정합니다. 종목코드를 모르면 search_stock으로 먼저 찾으세요.

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": {
      "stock_code": "<stock_code>"
    },
    "name": "get_stock_chart"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo캔들 개수 (기본값 30, 최대 200)
periodNo봉 주기 (기본값: day)
stock_codeYes6자리 종목코드 (예: 005930)
tick_scopeNoperiod=tick일 때 캔들당 틱 수 (기본값: 30)
minute_scopeNoperiod=minute일 때 분 단위 (기본값: 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.12.0
    • changedInput schema / properties / period / enum
      Previous value: -[
-  "day",
-  "week",
-  "month",
-  "minute"
-]New value: +[
+  "day",
+  "week",
+  "month",
+  "year",
+  "minute",
+  "tick"
+]
    • addedInput schema / properties / tick_scope
      Added value: +{
+  "description": "period=tick일 때 캔들당 틱 수 (기본값: 30)",
+  "enum": [
+    "1",
+    "3",
+    "5",
+    "10",
+    "30"
+  ],
+  "type": "string"
+}
  2. First observedv0.8.0

TDQS

A4.3/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses the use of adjusted prices (수정주가 반영) and references Kiwoom API codes, adding behavioral context. It does not contradict any annotations (none provided) and is consistent with a read-only operation.

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?

The description is concise, using one key sentence plus additional detail in the following sentences. It packs important information without redundancy, though the second sentence could be better structured for readability.

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?

Given no output schema, the description should ideally mention the response format (e.g., OHLCV data). It covers input parameters well but lacks details on what the returned data looks like, leaving the agent slightly uncertain about the output.

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

Parameters5/5

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

Schema coverage is 100%, but the description adds significant value by explaining the period enum values in Korean, clarifying default values for period, minute_scope, and tick_scope, and showing the relationship between period and the sub-parameters. This goes beyond the schema's enum lists.

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?

The description clearly states the tool retrieves candlestick chart data for a stock, specifies the resource (캔들 차트 데이터) and verb (조회), and differentiates from sibling tools like search_stock by advising to use search_stock if the stock code is unknown.

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?

The description explains when to use the tool (to get chart data) and provides a prerequisite (use search_stock if stock code unknown). It does not explicitly state when not to use, but the context makes it clear this is for chart data rather than simple price queries.

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

Deploy Server

Other Tools