Skip to main content
Glama

legal_research

Read-onlyIdempotent

Conduct complex Korean legal research across multiple dimensions: statutes, precedents, regulations, ordinances, amendment histories, and document review. Supports natural language queries and specialized research tasks.

Instructions

Korean-law-mcp — [⛓리서치] 다단계 법령 리서치 통합 — 여러 API를 병렬로 엮는 복합 질문 전용. task: full_research=도메인·법령명 불명확한 자연어 질문 폴백(기본값, 예 '음주운전 처벌 기준') | law_system=법률·시행령·시행규칙 3단+위임+별표(예 '관세법 체계') | action_basis=처분·허가의 법적 근거+해석례+판례+행심(예 '영업정지 근거') | dispute_prep=불복·소송 준비, 판례+심판례+도메인 결정례(예 '과세처분 불복') | amendment_track=개정 이력+신구대조+연혁(예 '2023년 개정 뭐 바뀜') | ordinance_compare=조례 전국 비교+상위법 적합성(예 '서울시 주차 조례') | procedure_detail=절차·수수료·별표서식(예 '건축허가 절차') | document_review=계약서·약관 조항 리스크+근거법령(text 필수). 단일 조회로 답이 되면 search_law/get_law_text 쓸 것.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
mstNo[amendment_track] 법령일련번호 (알고 있으면)
taskNo리서치 유형 (도구 설명의 task 표 참조). 미지정 시 full_researchfull_research
textNo[document_review 전용·필수] 검토할 계약서/약관 전문 텍스트
lawIdNo[amendment_track] 법령ID (알고 있으면)
queryNo자연어 질문/법령명/키워드 (예: '음주운전 처벌 기준', '관세법 체계'). document_review 외 모든 task에서 필수
domainNo[dispute_prep] 전문 분야 (tax=조세심판, labor=노동위, privacy=개인정보위, competition=공정위). 미지정 시 자동 감지
toDateNo[time_travel] 비교 종료 시점 YYYYMMDD
articlesNo[law_system] 함께 조회할 조문 번호 (예: ['제38조'])
fromDateNo[time_travel] 비교 시작 시점 YYYYMMDD
scenarioNo확장 시나리오. 미지정 시 쿼리에서 자동 감지. task별 호환: law_system=delegation·impact | action_basis=penalty | amendment_track=timeline·time_travel | ordinance_compare=compliance | full_research=customs·action_plan | procedure_detail=manual
parentLawNo[ordinance_compare] 상위 법령명. 미지정 시 자동 검색
maxClausesNo[document_review] 최대 분석 조항 수 (기본 15)
Behavior4/5

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds significant behavioral context: parallel API calls, multi-step research, and being a composite tool. No contradictions.

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 front-loaded with the main purpose and structured as a task list. While verbose, every sentence adds unique value for a 12-parameter tool. Could be slightly shorter but effective.

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 the tool's complexity (12 parameters, enums, multiple tasks) and full schema coverage, the description is comprehensive. Missing output format details, but no output schema exists. Overall adequate for agent selection.

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%. The description adds extensive semantics beyond parameter descriptions: explaining task-scenario compatibility, parameter usage contexts (e.g., [document_review required]), and default behaviors, enriching understanding.

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 clearly states the tool integrates multiple APIs for complex Korean legal research, and distinguishes itself from simpler sibling tools like search_law and get_law_text by explicitly advising to use those for single-lookup queries.

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?

The description provides explicit when-to-use guidance (complex questions requiring multiple APIs) and when-not-to-use (single-lookup cases), and lists specific task types with examples, enabling appropriate selection.

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/pragato-throwaway/korean-law-mcp-unclean'

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