Korean Law MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAW_API_OC | Yes | Your approved Open API authentication value (OC) from the Korean Law Open API. Required to call the API; setup/local checks can run without it. |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| korean_law_setupA | Check local configuration without network access or revealing the OC value. |
| search_legal_documentsA | Search Korean legal sources. eflaw defaults to current (nw=3); nw=1 is history, nw=2 is scheduled. Page results explicitly. Preserve the upstream IDs and dates. Optional filters must be documented for this target; OC/type/target cannot be overridden. This returns source data, not a legal conclusion. |
| get_legal_documentA | Retrieve a legal document. Use exactly one of document_id or mst. eflaw MST requires its YYYYMMDD effective_date from search; ID always selects current law. article is a six-digit JO code for law/eflaw (000200=Article 2, 001002=10-2). content is a slice of serialized upstream JSON, not necessarily valid JSON alone. Continue at next_offset when truncated; hashes must match across slices. |
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 3 tools
The three tools have clearly distinct roles: configuration check, legal source search, and document retrieval. Search vs. get is a standard and unambiguous split, and the descriptions reinforce how to choose between them.
All names use snake_case and are descriptive, but korean_law_setup does not follow the verb_noun pattern used by search_legal_documents and get_legal_document. The deviation is minor and still readable.
Three tools are well matched to a focused read-only Korean legal search server: setup, search, and fetch. Each tool has a clear purpose and there is no obvious filler.
The core search-and-retrieve workflow is covered, including pagination and article-level retrieval. Minor gaps exist, such as no explicit source-discovery or batch/document metadata tool, but agents can work around them via search.