Skip to main content
Glama

Koreanics: Korea law, Acts and bills in English

List laws in the database

list_laws
Read-onlyIdempotent

The South Korean statutes and enforcement decrees available in English, with slug, subject area, version in force and how many articles are translated. Paged: 50 per call by default; pass next_offset to continue, or filter by area.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_laws"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoOptional subject area to filter by, as shown in the results (e.g. "Employment & Labor").
limitNoLaws per page (default 50).
offsetNoStart position for paging (use next_offset from the previous result).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / area / description
      Previous value: -"Optional subject area to filter by, as shown in the results (e.g. \"Labor & Employment\")."New value: +"Optional subject area to filter by, as shown in the results (e.g. \"Employment & Labor\")."
    • addedInput schema / properties / limit
      Added value: +{
      +  "description": "Laws per page (default 50).",
      +  "maximum": 200,
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • addedInput schema / properties / offset
      Added value: +{
      +  "description": "Start position for paging (use next_offset from the previous result).",
      +  "minimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds value on top of that by disclosing the default page size, the continuation mechanism, and the shape of each returned row - context the annotations do not carry.

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?

Two sentences, both earning their place: the first front-loads what the tool returns, the second carries paging and filtering. No filler, no restatement of the tool name.

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?

With no output schema, the description correctly compensates by describing the returned fields. Read-only/idempotent behavior is covered by annotations, all parameters are documented, and paging is explained - nothing an agent needs in order to call this correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented in the schema, including that offset should come from the previous result. The description restates the 50 default and filtering but adds no syntax or format detail beyond the schema; minor terminology drift ('next_offset' vs the actual 'offset' parameter) slightly blurs rather than clarifies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource and enumerates what each row contains (slug, subject area, version in force, translated-article count), so an agent knows exactly what this returns. It does not explicitly contrast itself with search_law_articles or get_law_article, but the 'available in English' scope is concrete enough to distinguish it in practice.

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?

It gives clear operating context: results are paged at 50 per call by default, next_offset continues, and area filters. What it lacks is tool-selection guidance - nothing says when to browse here versus calling search_law_articles or get_law_article for a specific statute.

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