Skip to main content
Glama

set_kosis_key

Save your free KOSIS API key to the local user folder, enabling the server to retrieve Korean statistical data for graphs and maps.

Instructions

KOSIS 인증키를 이 컴퓨터 사용자 폴더에 저장한다(kosis.kr/openapi 에서 무료 발급).

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": {
      "key": "<key>"
    },
    "name": "set_kosis_key"
  }
}

Input Schema

NameRequiredDescriptionDefault
keyYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

B3/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It usefully discloses that a credential is persisted to a user folder on the local machine, which is a meaningful side effect, but it says nothing about whether an existing key is overwritten, whether the key is validated against the API, or how the secret is stored.

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?

One short sentence with the action front-loaded and the sourcing hint appended in parentheses. Nothing is wasted, though the reference to the key-issuing site would read better as a separate clause than a parenthetical.

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 one-parameter setup tool with no output schema, the description covers the essential what and where-to-get-it. It leaves out the setup-ordering relationship to the KOSIS query tools and the overwrite/validation behavior an agent would need before calling it twice.

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?

The schema has 0% description coverage for its single required parameter 'key'. The description only identifies it as the KOSIS authentication key and where to obtain one; it adds no format, length, or validity constraints, so it does not compensate for the coverage gap.

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?

The description states a specific verb and resource: it saves the KOSIS authentication key, and it names the storage target (this computer's user folder). It is instantly distinguishable from all listed siblings such as kosis_search or find_data, though it does not explicitly contrast with them.

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

Usage Guidelines3/5

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

The parenthetical that the key is issued free at kosis.kr/openapi helps an agent understand the prerequisite and source of the input. However, there is no statement that this must be run once before KOSIS data tools work, nor guidance on when to re-run it (e.g., replacing an expired key).

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