Skip to main content
Glama

Koreanics: Korea law, Acts and bills in English

Get the structure of a law (English)

get_law_overview
Read-onlyIdempotent

The shape of one South Korean statute or enforcement decree without its full text: official English name, version in force, how much is translated into English, its chapters and sections with the article ranges they cover, the linked enforcement decree or parent Act, and how many amendment bills are pending in the National Assembly (a count and a link, not what each bill changes). Works for laws whose English translation is still in progress. Use get_law_article for the text.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "law": "<law>"
    },
    "name": "get_law_overview"
  }
}

Input Schema

NameRequiredDescriptionDefault
lawYesLaw slug, e.g. "labor-standards-act" (see list_laws or search_law_articles).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

With read-only/idempotent annotations already covering safety, the description adds substantial behavioral detail: exact returned fields, that amendment bills are a count and link rather than bill contents, and that partial-translation laws are supported. Goes well beyond structured fields.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads the core purpose, then compactly enumerates returned data, adds the translation caveat, and finishes with the alternative tool. No filler sentences; the length is justified by the absence of an output schema.

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?

Covers exactly what the tool returns and what it omits (full text), which is critical since there is no output schema. Together with the fully described law parameter and annotations, an agent has everything needed.

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 schema already defines the law slug with example and lookup tools. The description adds modest semantic value by clarifying the law argument can be a statute or enforcement decree, but adds no syntax or format beyond schema. Baseline 3 plus small lift = 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?

States a specific verb (get) and resource (law overview/structure) for one South Korean statute or enforcement decree, and distinguishes from get_law_article by noting it excludes full text. The field list makes the scope unambiguous.

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?

Explicitly directs the agent to get_law_article for the text, establishing the primary alternative. Also notes it works for laws whose English translation is in progress, giving a clear usage condition. Routing is explicit even though other sibling tools are not mentioned.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources