Skip to main content
Glama
socialkim

korea-onegov-mcp

by socialkim

주제 브리핑(검색+전문 자동 수집)

onegov_research_topic
Read-onlyIdempotent

Search a topic and automatically retrieve the full text of top government documents, providing summaries and excerpts for efficient research.

Instructions

한 주제에 대해 검색을 돌린 뒤, 상위 문서 몇 건의 본문까지 자동으로 받아와 한 번에 돌려준다. "이 주제 정부 자료 정리해줘" 같은 요청에서 검색→전문조회 왕복을 줄여 준다.

Args:

  • query (string, 필수): 조사할 주제.

  • depth (number, 1~5, 기본 3): 본문까지 받아올 상위 문서 수. 많을수록 느리고 응답이 길다.

  • doc_type (string[], 선택) / ministry (string[], 선택) / from / to: onegov_search 와 동일한 필터.

  • chars_per_doc (number, 1000~10000, 기본 3000): 문서당 본문 길이 상한.

  • response_format ('markdown'|'json', 기본 markdown)

Returns: markdown: 검색 요약(총 건수·상위 목록) + 상위 depth 건의 본문 발췌(기관·발행일·원문링크 포함). json: { query, total, candidates[], documents[] }

Examples:

  • "AI 기본법 관련 정부 자료 정리해줘" → query="인공지능 기본법", depth=3

  • 단순히 목록만 필요하면 onegov_search 를 쓸 것(더 빠르다).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
toNo발행일 종료(YYYY-MM-DD)
fromNo발행일 시작(YYYY-MM-DD)
depthNo본문까지 받아올 문서 수
queryYes조사할 주제
doc_typeNo문서유형 필터(여러 개 가능). press_release=보도자료, policy=정책, law=법령, statistic=통계, info_disclosure=정보공개, faq=자주묻는질문, notice=고시·공고
ministryNo기관코드 배열
chars_per_docNo문서당 본문 길이 상한
response_formatNo출력 형식. 'markdown'은 사람이 읽기 좋은 요약(기본값), 'json'은 API 원본에 가까운 구조화 데이터.markdown
Behavior5/5

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

Annotations declare readOnlyHint=true and destructiveHint=false. The description adds behavioral context: it mentions the performance trade-off of depth (more documents = slower, longer response), the automatic fetching of full text, and the output format details (markdown vs json). No contradictions are present.

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?

The description is well-structured with clear sections (Args, Returns, Examples, usage notes). It front-loads the core purpose and provides necessary detail without redundancy. Every sentence adds value, including the comparison to the sibling tool.

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

Completeness5/5

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

Given the absence of an output schema, the description thoroughly explains the return format and content (search summary + top documents with metadata). It covers all 8 parameters (including filters), provides examples, and addresses when to prefer a sibling tool. The tool's complexity is fully addressed.

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 coverage is 100%, so baseline is 3. However, the description adds significant extra meaning: it explains that depth controls the number of full-text documents, chars_per_doc limits content length, and response_format offers two modes. It also clarifies that doc_type and ministry filters are shared with onegov_search, providing context beyond the 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?

The description clearly states the tool performs a search on a topic and automatically fetches the full text of top documents (depth). It distinguishes from the sibling onegov_search by explicitly noting that onegov_search is faster for simple lists.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use this tool (for topic briefing with full text) and when to use onegov_search instead (for list-only needs, which is faster). Examples illustrate typical usage.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/socialkim/korea-onegov-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server