Skip to main content
Glama
ChunSam

kiwoom-mcp-server

by ChunSam
OverviewSchemaSourceRelated ServersScoreDiscussionsAdmin
TypeScript
Local

장중 주체별 순매수 상위 (실시간)

get_foreign_intraday

Get real-time foreign investor net buying/selling rankings during trading hours, with filters for top N, market, direction, and unit (amount or quantity).

Instructions

정규장 중 어떤 주체가 지금 사고 있는 종목을 전 종목에서 뽑습니다 (키움 ka10063/ka10065). '오늘 외국인이 뭘 담고 있나', '장중 연기금 순매수 상위'처럼 실시간 수급을 볼 때 쓰세요. investor로 외국인(기본)·기관계·보험·투신·연기금등·기타법인을 고릅니다 — 개인·금융투자는 거래소가 장중에 공개하지 않아 조회할 수 없습니다. 값은 1,000주 단위 잠정치라 마감 후 확정치와 다릅니다(부호가 반대일 수도 있음) — 마감된 거래일 기준은 get_net_buy_rank, 종목을 이미 정했다면 get_investor_trend를 쓰세요.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topNo표시할 종목 수 (기본값 20, 최대 50)
unitNo정렬·표시 단위 (기본값 amount=백만원) — **investor=foreign에서만 유효**, 나머지 주체는 수량만 옵니다
marketNo시장 (기본값 all=전체). foreign은 키움이 코드 순으로 주므로 서버가 정렬합니다
investorNo투자자 주체 — foreign(외국인, 기본)/institution(기관계)/insurance(보험)/trust(투신)/pension(연기금등)/other_corp(기타법인). foreign만 금액·현재가까지 나옵니다
directionNobuy=순매수 상위(기본), sell=순매도 상위

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.44.1
    • addedInput schema / properties / investor
      Added value: +{
+  "description": "투자자 주체 — foreign(외국인, 기본)/institution(기관계)/insurance(보험)/trust(투신)/pension(연기금등)/other_corp(기타법인). foreign만 금액·현재가까지 나옵니다",
+  "enum": [
+    "foreign",
+    "institution",
+    "insurance",
+    "trust",
+    "pension",
+    "other_corp"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / market / description
      Previous value: -"시장 (기본값 all=전체 약 1,420종목). 키움이 코드 순으로 주므로 서버가 정렬합니다"New value: +"시장 (기본값 all=전체). foreign은 키움이 코드 순으로 주므로 서버가 정렬합니다"
    • changedInput schema / properties / unit / description
      Previous value: -"정렬·표시 단위 (기본값: amount=백만원)"New value: +"정렬·표시 단위 (기본값 amount=백만원) — **investor=foreign에서만 유효**, 나머지 주체는 수량만 옵니다"
  2. Addedv0.36.0

TDQS

A5/5.0
Behavior5/5

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

With no annotations provided, the description fully carries the transparency burden. It discloses that values are provisional in 1,000-share units, may differ from final values after market close, and can even have reversed signs. It also explains why certain investor types are not queryable, adding critical behavioral context.

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 front-loaded with the core purpose, followed by usage guidance, caveats, and alternatives. Every segment earns its place, using bold and em-dashes to emphasize key points without redundancy. Despite its length, it remains efficient for the complexity involved.

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?

Given the tool's complexity (5 parameters, 4 enums, no output schema), the description is complete enough for correct invocation. It covers the real-time scope, investor limitations, provisional value behavior, and explicit tool alternatives, ensuring an agent can decide when to use it and what to expect.

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?

Although schema coverage is 100%, the description adds significant meaning beyond the schema: it clarifies that the unit parameter is only valid for the foreign investor, that the market parameter results in server-side sorting, and that investors like individuals and financial investment are not supported. These details are not present in the schema property descriptions.

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 extracts stocks that a specific investor is currently buying during regular market hours ('어떤 주체가 지금 사고 있는 종목') and identifies the resource ('전 종목에서'). It also distinguishes from siblings by explicitly mentioning alternatives (get_net_buy_rank for settled days, get_investor_trend for specific stocks).

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

Usage Guidelines5/5

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

It provides explicit usage guidance: '실시간 수급을 볼 때 쓰세요' (use when viewing real-time supply/demand), and clearly contrasts with post-market and single-stock alternatives. It also states the exchange limitation: individual and financial investment investor types are unavailable during market hours.

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

Install Server

Other Tools