korean-law-alio-mcp

advanced_search

Filter Korean laws, administrative rules, or ordinances by type, ministry, or enforcement date. Combine keywords with AND/OR to target precise legal documents.

Instructions

[고급검색] 법령종류/부처/시행일 필터 검색. 복합 조건 시.

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>",
      "searchType": "<searchType>",
      "operator": "<operator>",
      "display": "<display>"
    },
    "name": "advanced_search"
  }
}

Input Schema

Name	Required	Description	Default
`query`	Yes	검색 키워드
`searchType`	Yes	검색 대상: law (법령), admin_rule (행정규칙), ordinance (자치법규), all (전체)	law
`fromDate`	No	제정일 시작 (YYYYMMDD)
`toDate`	No	제정일 종료 (YYYYMMDD)
`org`	No	소관부처코드
`operator`	Yes	키워드 결합 연산자	AND
`display`	Yes	최대 결과 개수
`apiKey`	No	법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Apr 26, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations provided. Description only mentions 'filter search' and 'complex conditions' but does not disclose behavior such as authentication requirements (apiKey is described in schema but not in description), rate limits, or result format. The burden falls entirely on the description, which is insufficient.

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?

Description is very short (one line), which is concise but risks being under-informative. It lacks structure and front-loads only a brief purpose. Could benefit from more detail without being verbose.

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

Completeness2/5

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

Given 8 parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, pagination, error handling, or how to use the apiKey. The tool is complex, so more detail is necessary.

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% with descriptions for each parameter. The tool description mentions filters (law type, department, date) which map to parameters, but adds little extra meaning. With full schema coverage, baseline is 3, and description does not significantly add beyond the schema.

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?

Description states it's for advanced search with filters on law type, department, and enforcement date, matching the name and distinguishing it from simpler search tools among siblings. However, it does not explicitly differentiate from sibling tools, and the phrasing '복합 조건 시' is vague.

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

Usage Guidelines2/5

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

No guidance on when to use this tool versus other search tools (e.g., search_law, search_ordinance). It does not provide explicit when-to-use or alternatives, leaving the agent to infer based on the name.

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

Deploy Server