openkrx-mcp

get_kosdaq_stock_base_info

Retrieve fundamental data for all KOSDAQ-listed stocks on a given base date. Specify the date in YYYYMMDD format to obtain key details.

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_stock_base_info"
  }
}

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

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description must shoulder the full transparency burden. It only says '조회합니다' (retrieves), which implies a read operation, but does not clarify whether the date must be a trading day, what the return payload looks like, or whether it returns all KOSDAQ stocks for that date.

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 a single sentence plus a parameter line, with no excessive detail. It is concise, front-loaded, and easy to parse.

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 simple one-parameter tool with an output schema, the description gives the purpose and essential date parameter. It could specify that it returns info for all KOSDAQ stocks on that date, but it is otherwise sufficient for an agent to invoke it correctly.

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 must explain basDd. It does this by specifying '기준일자 (YYYYMMDD)' (base date in YYYYMMDD format), which fully clarifies the single parameter.

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 uses the specific verb '조회' (retrieve) with a clear resource 'KOSDAQ 종목기본정보' (KOSDAQ stock basic info). This distinguishes it from sibling tools like get_kosdaq_stock_daily (daily price data) and get_kospi_stock_base_info (KOSPI base info).

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?

The description provides no guidance on when to use this tool versus alternatives. It only states what the tool does, with no mention of prerequisites, exclusions, or suitable scenarios.

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