Skip to main content
Glama
rubatoyd

io.github.rubatoyd/kosis-openapi-mcp

by rubatoyd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

kosis_collect

Fetch statistical table values from KOSIS and save them to xlsx, csv, json, or sqlite. Automatically adapts to each table's variable classification columns and axis levels.

Instructions

통계표 수치를 받아 xlsx/csv/json/sqlite 로 저장한다.

⚠️ 분류 축이 표마다 다르므로 열 구성이 가변이다 — 분류 이름이 그대로 열이 된다. 축 개수도 표마다 다르지만 obj_l2~obj_l8 을 비워 두면 자동으로 맞춘다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
endNo
nameNokosis
itemsNoALL
startNo
obj_l1NoALL
obj_l2No
obj_l3No
obj_l4No
obj_l5No
obj_l6No
obj_l7No
obj_l8No
org_idYes
prd_seYes
recentNo
tbl_idYes
formatsNo
out_dirYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changed
    • addedInput schema / properties / obj_l2
      Added value: +{
+  "default": "",
+  "title": "Obj L2",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l3
      Added value: +{
+  "default": "",
+  "title": "Obj L3",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l4
      Added value: +{
+  "default": "",
+  "title": "Obj L4",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l5
      Added value: +{
+  "default": "",
+  "title": "Obj L5",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l6
      Added value: +{
+  "default": "",
+  "title": "Obj L6",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l7
      Added value: +{
+  "default": "",
+  "title": "Obj L7",
+  "type": "string"
+}
    • addedInput schema / properties / obj_l8
      Added value: +{
+  "default": "",
+  "title": "Obj L8",
+  "type": "string"
+}
  2. First observedv0.1.0

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already indicate readOnlyHint=false, openWorldHint=true, and destructiveHint=false. The description adds useful behavior: saving to files, variable column structure, and auto-adjustment of axes. However, it does not disclose other behaviors such as file overwriting, authentication requirements, or rate limits. It adds some value beyond annotations but is not comprehensive.

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?

The description is concise with two sentences. The first sentence states the main purpose, and the second warns about variable columns. It is efficient and front-loaded, though the second sentence is a bit long and could be split for clarity.

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?

Given the tool's complexity (18 parameters, no output schema, no enums), the description is far from complete. It does not explain required parameters like org_id, tbl_id, or prd_se, nor optional ones like start/end/recent. The warning about variable columns is helpful, but the overall context is insufficient for an agent to call the tool correctly without further investigation.

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%, so the description must compensate. It explains obj_l2~obj_l8 auto-adjustment and the formats parameter implicitly (xlsx/csv/json/sqlite). However, it leaves the other 14 parameters (org_id, tbl_id, prd_se, start, end, recent, name, items, obj_l1) undocumented. This is a significant gap for a tool with 18 parameters.

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 clear verb+resource: receives statistics table values and saves them as xlsx/csv/json/sqlite. It also mentions the variable column structure, but does not differentiate from sibling tools like kosis_data or kosis_indicator_data, which may also fetch data. The purpose is specific but not distinguished from alternatives.

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 on when to use this tool vs alternatives. It provides a technical note about variable columns and auto-adjustment, but does not state when this tool is preferred over siblings like kosis_data. The agent is left to infer usage from the name and description.

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

Deploy Server

Other Tools