openkrx-mcp

get_kosdaq_index_daily

Retrieve daily KOSDAQ index series (e.g., KOSDAQ, KOSDAQ150) for a given base date (YYYYMMDD). Provides historical index values for market analysis and reporting.

Instructions

KOSDAQ 시리즈 지수 일별시세정보를 조회합니다.

Args: basDd: 기준일자 (YYYYMMDD)

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": {
      "basDd": "<basDd>"
    },
    "name": "get_kosdaq_index_daily"
  }
}

Input Schema

Name	Required	Description	Default
`basDd`	Yes

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jul 31, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations provided, the description must carry the full behavioral burden. It merely says 'retrieve' (조회), implying a read-only operation, but discloses nothing about authentication, rate limits, error behavior, or what exactly is included in 'daily price information.'

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 appropriately brief: a one-sentence purpose statement followed by a compact parameter definition. Every sentence earns its place; there is no filler or redundancy.

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?

For a simple one-parameter data retrieval tool with an output schema, the description covers the core purpose and parameter adequately. However, it lacks any usage guidance or behavioral context, and the large sibling set makes the absence of explicit differentiation a meaningful gap.

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?

The description's Args block explains that basDd is the base date in YYYYMMDD format, adding meaning beyond the bare schema property name and title. It does not define valid date ranges or trading-day constraints, but for a single parameter it is sufficiently informative.

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 clearly states the tool retrieves daily price information for KOSDAQ series indices, using a specific verb and resource. It implicitly differentiates from sibling tools like get_kospi_index_daily or get_krx_index_daily, though it does not explicitly contrast with them.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, exclusions, or any preference over sibling tools, leaving the agent to infer usage from the name alone.

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