Skip to main content
Glama

lawmadi-os

by io.github.peter120525-cmd

lookup_precedent

사건번호로 한국 판례를 조회합니다. 먼저 검증 자산(17,248건, 전부 law.go.kr 본문 대조 완료)을 보고, 없으면 law.go.kr 정본 색인(대법원 판례·헌재결정례 전수)에서 실재를 확인한 뒤 본문을 직접 받아옵니다. 응답의 source 필드가 근거의 강도를 가릅니다 — corpus 는 본문까지 대조된 것이고, authoritative_index 는 정본에서 실재를 확인하고 본문을 그 자리에서 받아온 것입니다. 법원·선고일·사건명·판시사항·판결요지·참조조문과 law.go.kr 원문 직결 링크를 돌려줍니다. LLM을 부르지 않는 결정론적 조회라 할루시네이션이 없습니다. 입력 예: '2020도3050', '대법원 2020. 3. 26. 선고 2020도3050 판결', '2016헌마90'. / Look up a Korean court case by docket number in Lawmadi's verified-asset corpus (17,248 precedents, each confirmed against law.go.kr). Returns court, decision date, case name, holding, summary, referenced articles and a direct law.go.kr full-text link. Deterministic — no LLM, no hallucination. Callable without an API key at preview depth (metadata + law.go.kr link + first 200 chars of the holding); a key unlocks the full holding, summary and referenced articles. / 키 없이도 미리보기 깊이로 조회됩니다 — 판시사항 전문·판결요지·참조조문은 키 발급 후 제공됩니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
case_noYesDocket number or full citation. Example: '2020도3050'.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

There are no annotations, so the description carries the full burden—and it delivers. It discloses the two-stage lookup strategy (corpus then authoritative_index), explains what the source field means, states that it is deterministic with no LLM, and details preview-vs-full results based on API key. This is unusually transparent.

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?

The description is front-loaded with purpose and organizes behavior logically, but the same information is repeated in Korean and English, and the API-key preview note is stated twice. The redundancy inflates length without adding semantic content.

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 only one required parameter and no output schema, the description still enumerates all returned fields, explains source-field semantics, covers authentication behavior, and states deterministic safety properties. It is complete enough for an agent to invoke and interpret correctly.

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% with one parameter, so baseline is 3. The description adds real value by listing multiple accepted input formats—'2020도3050', a full citation string, and '2016헌마90'—which goes beyond the schema's single example.

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?

The description opens with a specific verb and resource: '사건번호로 한국 판례를 조회합니다' and 'Look up a Korean court case by docket number.' It clearly distinguishes itself from sibling lookup_statute by focusing on precedents rather than statutes, and the scope of law.go.kr sources is explicit.

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 clearly implies when to use this tool: when a Korean court case must be looked up by docket number, especially when deterministic, non-hallucinated results are needed. It also explains the API-key depth difference. However, it does not explicitly name sibling alternatives or state when not to use it.

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

All lawmadi-os toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A3.8/5.0
Disambiguation4/5

Most tools target clearly distinct resources (statutes, precedents, bar exam, documents, content, account), and cross-references in descriptions explicitly disambiguate similar actions like search vs lookup_statute vs lookup_precedent. A few close pairs exist (ask vs ask_expert, latest_content vs get_daily_content, bar_exam_search vs get_exam_answer), but each pair has clear differentiators.

Naming Consistency4/5

The set predominantly follows snake_case verb_noun naming (get_account, lookup_statute, verify_citations, generate_document). Minor deviations like latest_content (no verb) and bar_exam_search (noun-first) break the pattern, but the overall convention is readable and predictable.

Tool Count4/5

At 19 tools, the surface is on the heavier side but each tool addresses a distinct need across a broad legal domain (Q&A, research, document generation, bar exam corpus, content, account management). The count feels justified for the stated scope, though it approaches the upper boundary of reasonable.

Completeness4/5

The server covers the main legal workflows well: Q&A (ask, chat_leader), research (lookup_statute, lookup_precedent, search, verify_citations), document drafting (generate_document), and bar exam prep (bar_exam_search, get_exam_answer). Minor gaps exist, such as no browse/list-all endpoints for statutes or precedents and no way to manage generated documents, but agents can work around these.

Resources