Skip to main content
Glama

kosis_items

Retrieve KOSIS statistical table items, classification levels, and periods by organization and table ID to inspect available dimensions before building charts or maps.

Instructions

KOSIS 통계표의 항목(itmId)·분류(objL1…)·기간을 본다.

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": {
      "orgId": "<orgId>",
      "tblId": "<tblId>"
    },
    "name": "kosis_items"
  }
}

Input Schema

NameRequiredDescriptionDefault
orgIdYes
tblIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden and discloses almost nothing. It does not state whether the call is read-only, whether an API key (cf. set_kosis_key) must be set first, what the response shape looks like, or how items/classifications/periods relate to each other.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single short, front-loaded sentence with no filler, so nothing is wasted. But that brevity comes from under-specification rather than disciplined compression — the one sentence cannot carry the tool's three required parameters.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

There is no output schema and no annotations, and both required parameters are undocumented, so the description is the only source of information and it leaves major gaps. An agent can guess the domain but not how to obtain orgId/tblId or what will come back.

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

Parameters2/5

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

Schema description coverage is 0% and the description never explains orgId or tblId, the two required parameters, nor where their values come from. Worse, the identifiers it does mention (itmId, objL1) are not input parameters at all, so an agent could mistake them for arguments.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource (KOSIS statistical table items, classifications, periods) and implies a read action via '본다', which is more than a tautology. However the verb is generic and nothing distinguishes it from the sibling kosis_search, which plausibly also surfaces table metadata.

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?

There is no when-to-use guidance at all: no mention of prerequisites (e.g. prior kosis_search to obtain tblId, or set_kosis_key for auth) and no routing against alternatives like kosis_search or guide. The agent must infer the entry point from sibling names alone.

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