Skip to main content
Glama
Korean Law MCP Server

Korean Law MCP Server

by yunhyok

search_legal_documents

Read-onlyIdempotent

Search Korean legal sources by query and target to retrieve paginated official statutes, administrative rules, ordinances, precedents, and decisions with source IDs and dates.

Instructions

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.

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": {
      "query": "<query>"
    },
    "name": "search_legal_documents"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
queryYes
targetNoeflaw
displayNo
parametersNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, open-world safety profile, so the description correctly spends its words elsewhere: it warns that output is source data rather than a legal conclusion, that upstream IDs and dates must be preserved, and that OC/type/target cannot be overridden. Those are non-obvious behavioral constraints an agent could not get from the annotations or schema.

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

Conciseness3/5

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

It is short and front-loads the purpose, but several sentences read as implementer notes rather than agent guidance ('Optional filters must be documented for this target'), and 'Page results explicitly' is ambiguous. Fragments without subjects make the operational rules harder to parse than necessary.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return values need not be described, and the source-data caveat is a useful addition. However, for a 5-parameter open-world search with 0% schema coverage and an eight-value target enum, the description leaves the target choices and paging/display controls substantially unexplained.

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 description coverage is 0%, so the description carries the burden and only partly meets it: it documents the nw values and the target-override restriction, but leaves `query`, `page`, and `display` unexplained and gives no meaning for the eight target enum values other than eflaw. 'Page results explicitly' hints at pagination without defining behavior.

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 first sentence gives a specific verb and resource (search Korean legal sources), and the description adds scope details (eflaw/law/admrul... targets implied, source data vs. legal conclusion). It does not explicitly distinguish itself from the sibling get_legal_document or korean_law_setup, so an agent must infer that this is the discovery step and those are retrieval/setup.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is real usage context: eflaw defaults to current (nw=3), nw=1 is history, nw=2 is scheduled, and results should be paged explicitly. But no when-to-use vs. get_legal_document / korean_law_setup, no prerequisites, and 'nw' is never tied to a schema field, so the agent must guess it belongs inside the opaque `parameters` bag.

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