Skip to main content
Glama
Sign In
geo-figure-mcp

geo-figure-mcp

by skyblue3925-svg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

list_bundled_data

Lists built-in KOSIS statistics by topic, period, item, and classification without an API key, so you can locate the right dataset before querying KOSIS directly.

Instructions

키 없이 쓰는 내장 KOSIS 통계 목록(주제·기간·항목·분류). KOSIS 를 직접 부르기 전에 먼저 여기서 찾는다.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_bundled_data"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden, and it does disclose the important trait that no API key is required (contrasting with set_kosis_key) and that the data is pre-bundled rather than live. It says nothing about the response shape, how exhaustive the catalog is, or whether results can go stale, which leaves meaningful gaps for a no-annotation tool.

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

Conciseness5/5

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

Two compact sentences with the resource definition first and the usage rule second; every clause carries information and nothing is padded.

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

Completeness4/5

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

For a zero-parameter list tool with no output schema, the description covers what the catalog contains, that it needs no key, and when to consult it. It could say more about the structure or scale of the returned list, but nothing essential to invoking it is missing.

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

Parameters4/5

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

The tool takes zero parameters, so the baseline is 4 and there is nothing the description needs to disambiguate. The parenthetical does usefully signal the facets exposed in the returned records.

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 gives a clear verb+resource: a built-in ('내장') KOSIS statistics catalog usable without an API key, and enumerates what it covers (topics, periods, items, classifications). It does not explicitly differentiate itself from lookalike siblings such as kosis_items or find_data, so an agent still has to infer the boundary.

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?

'KOSIS 를 직접 부르기 전에 먼저 여기서 찾는다' gives an explicit ordering rule: consult this catalog before hitting KOSIS directly. It is clear when to reach for it, but names no exclusion or explicit alternative among the many sibling tools.

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