Skip to main content
Glama
memorise8

law-search-mcp

by memorise8

search_precedents

Search Korean court precedents by keyword. Retrieve case names, court info, and continue with detail lookup via law.go.kr Open API.

Instructions

한국 법원 판례 목록을 키워드로 검색합니다.

law.go.kr 공식 Open API를 통해 판례를 검색하고 기본 정보 목록을 반환합니다.
검색 결과에는 사건명, 법원 및 선고 정보, 판례일련번호(precSeq)가 포함됩니다.
판례일련번호를 사용하여 get_precedent_detail()로 상세 내용을 조회할 수 있습니다.

Parameters:
    query: 검색 키워드 (예: "손해배상", "계약해제", "부당해고")
    max_results: 최대 결과 수 (기본값: 20, 최대 100)
    page: 페이지 번호 (기본값: 1)
    sort: 정렬 기준 (예: "date" 선고일자순, 기본값: 관련도순)
    org: 법원종류코드 (예: "400201" 대법원, 빈 문자열이면 전체)
    date_range: 선고일자 범위 (형식: YYYYMMDD~YYYYMMDD, 예: "20200101~20231231")

Returns:
    검색된 판례 목록 (사건명, 법원/선고 정보, 판례일련번호 포함)
    판례일련번호로 get_precedent_detail(precedent_id)를 호출하면 상세 내용을 조회할 수 있습니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
max_resultsNo
pageNo
sortNo
orgNo
date_rangeNo

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It mentions using a public API and returning a list of basic information, indicating a read-only operation. It does not discuss rate limits or authentication, but for a search tool, the core behavior is clear and no contradictions exist.

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?

The description is well-organized: a brief purpose statement, then source and output explanation, then a labeled parameter list. Some repetition occurs (serial number usage mentioned twice), but it remains concise and front-loaded with key information.

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?

Given 6 parameters, no schema descriptions, and an output schema, the description covers the essential aspects: each parameter, example values, and the output structure. It connects to the sibling tool. However, it could be more complete by clarifying pagination behavior or error handling, but it is adequate for a search tool.

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

Parameters5/5

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

Schema description coverage is 0%, so the description fully compensates by listing each parameter with examples and default values. It explains query, max_results, page, sort, org, and date_range with concrete usage hints, adding meaning well beyond the bare schema.

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?

Description clearly states the tool searches Korean court precedents by keyword, specifying the source (law.go.kr official API) and the returned information (case name, court, serial number). It explicitly differentiates from sibling get_precedent_detail by indicating that the serial number can be used for detailed lookups.

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?

The description provides clear context on when to use this tool (for keyword-based searches) and implies that get_precedent_detail should be used for full details. It does not explicitly state when not to use it, but the differentiation is sufficient for an agent to understand the tool's role.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/memorise8/law-search-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server