Browse South Korean national statistics classification trees by topic or organization, one level at a time, to locate KOSIS categories and parent IDs for further data queries.
KOSIS 통계목록(주제별/기관별 분류 트리)을 한 단계씩 탐색합니다.
| Name | Required | Description | Default |
|---|---|---|---|
| vw_cd | No | 목록 구분: MT_ZTITLE(주제별), MT_OTITLE(기관별) 등 | MT_ZTITLE |
| parent_id | No | 상위 목록 ID (최상위는 빈 값이 아니라 '0') | 0 |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are present, so the description carries the full behavioral burden. It usefully discloses that this is a step-by-step (iterative) tree traversal, which is behavior beyond the schema, but it does not state read-only safety, what is returned, or how to proceed after a call.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
A single efficient sentence, front-loaded with the resource and the traversal mode. It avoids waste, though it is arguably too terse for a tool with no annotations.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple two-parameter tool with a fully documented schema, the description covers the core purpose. It omits important operational context: that it returns child nodes, how to use parent_id='0' for the root, and that repeated calls are needed to reach a table.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%: both vw_cd and parent_id are fully documented with defaults and enum-like values. The description adds no parameter meaning beyond the schema, so the baseline of 3 is appropriate.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
States a specific verb+resource: exploring the KOSIS statistics list, which is a theme/institution classification tree. The phrase '한 단계씩' (one step at a time) signals hierarchical traversal and distinguishes it from search-style siblings, though no sibling is named explicitly.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage is implied by '한 단계씩 탐색' – the agent can infer this tool is for iterative top-down browsing rather than searching or fetching data. However, no explicit when-to-use guidance or alternatives (e.g., kosis_search) are provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.