Skip to main content
Glama
Sign In

Lifelaw Korean Law (라이프로 법령)

by kr.lifelaw
OverviewDiscussionsAdmin

Get law article (조문 원문)

get_article
Read-onlyIdempotent

Get the text of an article of a Korean law in force, verbatim and unedited from the Ministry of Government Legislation (법제처). The law needs its official name, in Korean or the official English title (e.g. 근로기준법, Labor Standards Act). With lang en (default for an English law name) it gives the official English translation, a notice on whether that translation matches the Korean version in force, and the legally binding Korean original. edition 시행예정 gives the article of a promulgated amendment not yet in force (check whether one exists with get_law_status).

Input Schema

NameRequiredDescriptionDefault
lawYesOfficial law name in Korean or English. E.g. 근로기준법, 주택임대차보호법 시행령, Labor Standards Act
langNoAnswer language. en: official English translation + version check + Korean original / ko: Korean. Default: en if the law name is English
branchNoBranch number (the 2 in 제6조의2, Article 6-2). Omit if already in article
articleYesArticle number. E.g. 36, 제36조, 제6조의2, Article 76-2
editionNo현행 = in force (default) / 시행예정 = promulgated but not yet in force

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / article / description
      Previous value: -"조 번호. 예: 36, 제36조, 제6조의2"New value: +"Article number. E.g. 36, 제36조, 제6조의2, Article 76-2"
    • changedInput schema / properties / branch / description
      Previous value: -"가지번호(조의2 의 2). 조 번호에 '의'를 넣었다면 생략"New value: +"Branch number (the 2 in 제6조의2, Article 6-2). Omit if already in article"
    • changedInput schema / properties / edition / description
      Previous value: -"현행(기본) / 시행예정(공포됐지만 아직 시행 전인 판)"New value: +"현행 = in force (default) / 시행예정 = promulgated but not yet in force"
    • addedInput schema / properties / lang
      Added value: +{
+  "description": "Answer language. en: official English translation + version check + Korean original / ko: Korean. Default: en if the law name is English",
+  "enum": [
+    "ko",
+    "en"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / law / description
      Previous value: -"법령 정식 명칭. 예: 근로기준법, 주택임대차보호법 시행령"New value: +"Official law name in Korean or English. E.g. 근로기준법, 주택임대차보호법 시행령, Labor Standards Act"
  2. Changed1 schema field changed
    • addedInput schema / properties / edition
      Added value: +{
+  "description": "현행(기본) / 시행예정(공포됐지만 아직 시행 전인 판)",
+  "enum": [
+    "현행",
+    "시행예정"
+  ],
+  "type": "string"
+}
  3. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds substantive content: the answer is verbatim and unedited, en returns the official English translation plus a version-match notice plus the binding Korean original, and 시행예정 returns not-yet-in-force text. That is real behavioral context beyond the structured fields, especially valuable since there is no output schema.

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?

Front-loads the core action and scope in the first sentence, then layers the lang and edition behavior. It is dense and slightly long, but every sentence carries information an agent needs; nothing is filler.

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?

For a read tool with five parameters and no output schema, the description covers what is returned and the two edition modes well. Minor gaps remain: no mention of what happens when the law name is ambiguous or the article does not exist.

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%, so the baseline is 3; the description still adds meaning by explaining why lang defaults to en for English law names and what edition 시행예정 means operationally (promulgated but not in force). It does not add anything for article or branch, which the schema already covers well.

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?

States a specific verb and resource ('Get the text of an article of a Korean law in force') plus provenance ('verbatim and unedited from the Ministry of Government Legislation'). This clearly separates it from search_law (finding laws) and get_law_status (checking amendment status), which the description itself references.

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?

Gives clear context for the 시행예정 path and explicitly tells the agent to first check with get_law_status whether a promulgated amendment exists. It also explains the lang default rule for English law names. It does not spell out when to prefer this over siblings like get_document, but the core usage routing is present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Lifelaw Korean Law (라이프로 법령) toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources