law-openapi-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LAW_OC | Yes | The OC value from the National Law Information Center Open API (open.law.go.kr). It is the part before '@' in the registered email. |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| law_statusA | 연결 점검 — |
| law_targetsA | 다룰 수 있는 갈래와 갈래별 실측 스키마·주의사항. 갈래마다 응답 태그와 식별자 파라미터가 다르고 이름에서 유추할 수 없다 — 이 도구가 그 표다. |
| law_searchA | 법령·판례 등 한 갈래를 검색한다. Args:
target: 갈래 코드. law(현행법령)·admrul(행정규칙)·ordin(자치법규)·prec(판례)·
detc(헌재결정례)·expc(법령해석례)·trty(조약)·eflaw·elaw·lsStmd.
|
| law_bodyA | 식별자 1건의 본문을 받는다(조문·판시사항·질의요지 등). Args:
target: 갈래 코드.
doc_id: 목록 결과의 일련번호. 갈래마다 파라미터명이 MST/ID 로 다르지만
이 도구가 알아서 맞춘다.
include_articles: 조문 목록을 함께 돌려줄지(법령·자치법규에만 있다).
ef_date: 시행일법령(eflaw) 전용 — 목록의 |
| law_collectA | 갈래 × 검색어의 합집합을 모아 파일로 저장한다. ⚠️ |
| law_citationD | 한 건을 서지(인용) 필드로 매핑한다 — 발령주체·호·공포일·시행일·제정기관. 목록에서 1건을 다시 찾아 매핑한다. 서지관리 도구(Ibis 의 |
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 6 tools
Each tool has a distinct role: connectivity check, schema map, single-target search, document body retrieval, bulk collection, and citation mapping. Overlapping actions such as search vs. collect are clearly differentiated by single-result versus multi-axis file output.
All tools follow a uniform law_ prefix with short, lowercase, predictable names. Some names are nouns and some are verbs, but the pattern is consistent and easy to infer.
Six tools cover the full workflow without redundancy: verify, discover, search, retrieve, collect, and cite. The count is well within the ideal range for a focused API wrapper.
The set supports a complete read-only workflow for legal documents: discovering targets, querying, fetching full bodies, bulk collection, and citation export. No obvious missing operation would prevent an agent from accomplishing the core domain tasks.