korean-notice-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_DATA_DIR | Yes | Absolute path to the folder containing notice files (HWP, HWPX, TXT, MD, CSV). The server only reads files inside this folder. Example: C:\Users\me\Documents\공고 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_noticeA | 공고문(TXT/MD/HWPX/HWP) 텍스트와 표를 원문 위치·해시와 함께 읽습니다. PDF 제외. |
| extract_requirementsA | 공고의 제출서류(필수/조건부)·신청기간·자격 후보와 원문 근거를 추출합니다. 결과는 검토가 필요합니다. |
| compare_noticesA | 전년도와 올해 공고의 제출서류·신청기간 변화와 주요 변경 문구를 중요도 순으로, 양쪽 원문 근거와 함께 비교합니다. |
| get_evidenceB | 동일한 해시의 문서에서 위치에 해당하는 원문을 확인합니다. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool serves a distinct purpose: reading a notice, extracting structured requirements, comparing notices across years, and retrieving evidence by hash/location. No two tools overlap in function, and the descriptions clearly differentiate them.
All tool names follow a consistent verb_noun pattern in snake_case: read_notice, extract_requirements, compare_notices, get_evidence. This is predictable and easy to reason about.
With only 4 tools, the server is tightly scoped to the analysis of Korean notices. Each tool is necessary and non-redundant, and the count is appropriate for the domain without feeling sparse or bloated.
The tool set covers the full lifecycle of notice analysis: reading the raw document, extracting key requirements, comparing with previous years, and verifying evidence. There are no obvious gaps for the stated purpose, and the workflow is complete.