Skip to main content
Glama
datagokr-dev

datagokr

by datagokr-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

search

Read-only

Find Korean public datasets by topic from data.go.kr, with optional type/provider filters. Returns summary counts and ranked candidates with metadata for inspection.

Instructions

주제로 공공데이터를 원격 검색합니다. Search the remote catalog by topic. query: 자연어 / topic; n: 1~20; dtype: FILE/API/STD; org: 기관명 / provider; fields: 모두 필요한 컬럼 / required columns. 반환 / Returns: {summary, results}. summary는 n으로 자르기 전 후보의 주제·데이터셋 수와 유형·기관 분포·의도 힌트입니다. Summary counts candidate groups/datasets before n, with type/provider distributions and intent hints. results: id, title, org_nm, access_kind, page_url, matched_fields, desc_short(설명 앞 120자 / first 120 characters, no newlines), top_columns(등록순 최대 5개 / first 5 registered columns), portal_updated(ISO date or null), org_level(national/local). group_count는 대표 포함 후보 멤버 수, group_ids는 순위순 최대 60개 id입니다. Group count includes the representative; group_ids contains up to 60 ranked member ids. 펼치기는 group_ids의 id를 show로 조회 / Inspect each group_ids member with show. 지역·API/파일 의도는 서버가 추출하며 dtype/org를 주면 더 정확합니다. The server infers region and API/file intent; explicit dtype/org filters are more precise. 예시 / Example: query='전국 주차장'.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nNo
orgNo
dtypeNo
queryYes
fieldsNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.1.4
    • addedOutput schema / additionalProperties
      Added value: +true
    • removedOutput schema / properties
      Removed value: -{
-  "result": {
-    "items": {
-      "additionalProperties": true,
-      "type": "object"
-    },
-    "type": "array"
-  }
-}
    • removedOutput schema / required
      Removed value: -[
-  "result"
-]
    • removedOutput schema / x-fastmcp-wrap-result
      Removed value: -true
  2. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

readOnlyHint=true already covers the safety profile. The description adds real behavioral context beyond it: the summary counts candidate groups/datasets before the n limit, group_count includes the representative, group_ids is capped at 60 ranked ids, and server-side intent inference occurs. Missing only error/empty-result behavior.

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

Conciseness3/5

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

Front-loaded and organized, but the bilingual duplication roughly doubles the length and some return-field detail overlaps with the output schema. Efficient in content, less so in size.

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?

Despite an output schema existing, the description documents the notable return fields and grouping semantics that matter for calling it correctly, plus the dtype/org inference behavior. Complete enough for a search tool; only error handling is absent.

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%, so the description carries the full burden and does so: it defines query as natural language/topic, n as 1-20, dtype as FILE/API/STD, org as provider name, and fields as required columns. This fully compensates for the undocumented schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource in both Korean and English ('원격 검색 / Search the remote catalog by topic'), and explicitly routes the follow-up inspection to the sibling 'show'. An agent can distinguish this from show/get/fetch without opening any schema.

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 concrete when-to-use guidance: inspect group members via 'show', and supply dtype/org explicitly for more precise results since the server otherwise infers region and API/file intent. Lacks explicit when-not-to-use framing, but the alternative routing is clear.

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