Skip to main content
Glama
socialkim

korea-onegov-mcp

by socialkim

문서 전문 조회

onegov_get_document
Read-onlyIdempotent

Retrieve the full text, attachments, related laws, and related documents of a Korean government document by its UUID from search results.

Instructions

문서 id로 전문(본문)과 첨부·관련법령·연관문서를 가져온다. id는 onegov_search 결과의 id 필드(UUID)다.

Args:

  • id (string, 필수): 문서 UUID.

  • max_body_chars (number, 기본 8000, 최대 40000): 본문 최대 길이. 길면 잘리고 안내가 붙는다.

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

Returns: markdown: 제목 · 메타(기관/발행일/원문링크/공공누리 유형/관련법령) · 본문 · 첨부 · 연관 문서. json: { id, doc_type, title, summary, body, ministry_name, published_at, source_url, kogl_type, kogl_notice, attachments[], law_ref[], region, links{related_by_law[], same_ministry_recent[]} }

Examples:

  • 검색 후 "이 공고 신청 자격 알려줘" → 해당 결과의 id로 호출

  • 쓰지 말 것: 아직 문서를 특정하지 못했을 때(→ onegov_search 먼저)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes문서 UUID (onegov_search 결과의 id)
max_body_charsNo본문 최대 길이
response_formatNo출력 형식. 'markdown'은 사람이 읽기 좋은 요약(기본값), 'json'은 API 원본에 가까운 구조화 데이터.markdown
Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description adds key behaviors: body truncation with max_body_chars, response_format options (markdown vs json) with their output details, and return structure. No contradictions with annotations.

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?

Well-structured with Args, Returns, and Examples sections. Front-loaded main purpose. Slightly verbose in Returns but each line provides useful detail. Efficient overall.

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 return formats and includes examples. It also covers usage context and constraints, making it complete for agent understanding.

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 coverage is 100% with parameter descriptions. The description adds context: id is from onegov_search, max_body_chars truncation behavior and limits, response_format differences. This adds meaningful detail beyond the schema, justifying a 4.

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 retrieves full text, attachments, related laws, and related documents by document ID. It explicitly links the ID to onegov_search results, distinguishing it from sibling tools like onegov_search and search.

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?

Provides explicit when-to-use: after onegov_search with a specific document ID. Also includes a 'do not use' example: when document has not been identified yet, directing to onegov_search first. This gives clear guidance on alternatives.

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