Skip to main content
Glama
kgy0617

ECOS MCP Server

by kgy0617
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

통계표 검색·탐색

search_statistic_tables
Read-onlyIdempotent

Find Korean macroeconomic statistics table codes and names by keyword or explore the classification tree. Search locally for instant results, filter to searchable tables, and navigate parent-child categories.

Instructions

통계표 이름으로 통계표코드(STAT_CODE)를 검색하거나, 통계표 분류 트리를 탐색합니다.

ECOS 통계표 전체의 로컬 인덱스를 사용하므로 API 호출 없이 즉시 응답합니다.
- keyword 지정: 이름 검색. 띄어쓰기로 나눈 단어가 모두 포함된 통계표를 관련도 순으로 반환
  ("소비자 물가" → "소비자물가지수"). parent_code를 함께 주면 그 분류 아래에서만 검색합니다.
- keyword 없이 parent_code 지정: 해당 분류의 직속 하위 항목 반환 (분류 노드 포함)
- 둘 다 없음: 최상위 분류 목록 반환

Args:
    keyword: 검색할 통계명 또는 키워드 (예: "물가", "금리", "환율", "경상수지")
    parent_code: 상위 분류 STAT_CODE (예: "0000000001")
    searchable_only: keyword 검색 시 실제 데이터 조회가 가능한 통계표(SRCH_YN='Y')만 반환 (기본값: True)
    limit: keyword 검색 시 최대 반환 개수 (기본값: 20)

Returns:
    통계표 목록 (STAT_CODE, STAT_NAME, CYCLE, SRCH_YN 등)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
keywordNo
parent_codeNo
searchable_onlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already mark it read-only and idempotent; the description adds useful behavioral detail: it uses a local index, responds immediately without an API call, returns relevance-ordered results, and filters by SRCH_YN. This is consistent with the annotations and adds context beyond them, though it doesn't disclose edge cases such as invalid parent_code behavior.

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 structure is clear: purpose, behavioral note, three bullet modes, Args, Returns. It is longer than minimal but every section adds value; a small redundancy is repeating defaults that already exist in the schema.

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?

With no output schema, it lists the returned fields (STAT_CODE, STAT_NAME, CYCLE, SRCH_YN) and explains the three call patterns, so an agent can invoke it correctly. It could be slightly more complete by explicitly routing to a sibling tool for other search needs, but that is more a usage-guideline gap than a completeness failure.

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

Parameters5/5

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

Schema description coverage is 0%, but the Args section fully compensates by explaining all four parameters, giving example values (물가, 금리, 0000000001), and defining searchable_only and limit semantics with defaults. This gives an agent everything needed to fill the parameters correctly.

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 searches statistic tables by name and traverses the statistic-table classification tree, returning STAT_CODE values. This is clear, though it does not explicitly distinguish itself from siblings like search_statistics or search_statistic_word, so it falls just short of full marks.

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?

It gives concrete usage modes: keyword for name search, parent_code for direct children, neither for root categories, and combined for scoped search. It notes the local-index/no-api-call property as a context cue, but it never names an alternative tool or says when not to use this one.

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