Skip to main content
Glama

kosis_search

Search KOSIS national statistical tables by keyword for province, city, county, and district data. Requires an authentication key; check bundled data first.

Instructions

KOSIS 국가통계포털에서 통계표를 찾는다(시·도·시·군·구 통계). 인증키 필요 — 먼저 list_bundled_data 를 본다.

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": {
      "query": "<query>"
    },
    "name": "kosis_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYes찾을 말. 예: 주간인구, 발전량 시도, 외국인 주민

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.6/5.0
Behavior3/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; it does disclose the auth-key requirement and the ordering constraint relative to list_bundled_data, which is real behavioral value. However, it says nothing about the shape of the results (e.g., whether it returns table IDs to feed into kosis_items), pagination, or failure behavior when the key is missing.

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

Conciseness4/5

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

Two short, front-loaded sentences with no filler; the purpose comes first and the prerequisite second. It is slightly under-specified rather than verbose, which is the preferable failure mode here.

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 single-parameter search tool with no output schema, the description covers purpose, auth requirement, and the immediate prerequisite. It is still incomplete on the downstream workflow — an agent cannot tell from this text that results likely feed into kosis_items, nor what a successful response looks like.

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

Parameters3/5

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

Schema coverage is 100% for the single query parameter, which already includes an example of acceptable values. The description adds only the domain framing (regional statistics) and does not extend the parameter's meaning beyond the schema, so the baseline 3 applies.

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?

States a specific verb and resource — searching statistical tables in the KOSIS portal — and narrows scope to regional (시·도·시·군·구) statistics. It does not explicitly distinguish itself from lookalike siblings such as kosis_items or find_data, so it stops short of a 5.

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

Usage Guidelines4/5

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

Gives a prerequisite (an authentication key is required) and a concrete routing hint — check list_bundled_data first — which tells the agent what to do before invoking. It stops short of 5 because there is no explicit when-not guidance or named alternative for the case where the desired table is already known.

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