Skip to main content
Glama
socialkim

korea-onegov-mcp

by socialkim

특정 부처 최신 자료

onegov_ministry_latest
Read-onlyIdempotent

Retrieve recent public documents from Korean ministries, sorted by date. Filter by ministry code, document type, query, or time range.

Instructions

한 부처(또는 여러 부처)의 최신 공개자료를 발행일 역순으로 가져온다. "국토부 요즘 뭐 냈어?" 같은 질문에 쓴다.

Args:

  • ministry (string[], 필수): 기관코드 배열(예: ["MOLIT"]). 코드는 onegov_list_ministries 로 확인.

  • doc_type (string[], 선택): 특정 유형만(예: ["press_release"]).

  • query (string, 선택): 부처 내에서 다시 좁힐 검색어.

  • days (number, 1~365, 선택): 최근 N일로 제한. 지정하면 from 을 자동 계산한다.

  • size (number, 1~50, 기본 20) / page (number, 기본 1)

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

Returns: onegov_search 와 동일한 형식(항상 최신순 정렬).

Examples:

  • "국토부 최근 보도자료" → ministry=["MOLIT"], doc_type=["press_release"], days=30

  • "중기부가 이번 달 낸 공고" → ministry=["MSS"], doc_type=["notice"], days=30

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
daysNo최근 N일로 제한
pageNo
sizeNo
queryNo부처 내 추가 검색어
doc_typeNo문서유형 필터(여러 개 가능). press_release=보도자료, policy=정책, law=법령, statistic=통계, info_disclosure=정보공개, faq=자주묻는질문, notice=고시·공고
ministryYes기관코드 배열(필수)
response_formatNo출력 형식. 'markdown'은 사람이 읽기 좋은 요약(기본값), 'json'은 API 원본에 가까운 구조화 데이터.markdown
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds behavioral information: returns latest items by date, supports pagination and response format selection, and mentions sorting. This adds value beyond the annotations.

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 Args, Returns, and Examples sections. It is concise yet informative, with no redundant sentences. Every sentence adds value.

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?

Given 7 parameters and no output schema, the description explains the return format (same as onegov_search, sorted by date) and response format options. It is sufficiently complete for the tool's purpose, though could mention error handling.

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?

Schema description coverage is 71%. The description provides additional context for parameters: ministry example code, doc_type list, days range, and examples mapping queries to parameters. This compensates for the uncovered parameters and adds meaning.

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 fetches the latest public documents from one or more ministries, sorted by publish date descending. It provides a concrete use case example ('국토부 요즘 뭐 냈어?') and distinguishes from siblings like onegov_search by focusing on 'latest' from specific ministries.

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?

The description provides clear context for when to use the tool with examples and parameter details. It does not explicitly state when not to use it or mention alternatives, but the examples effectively guide 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