korean-privacy-law-mcp

get_constitutional_decision_text

Retrieve the full text of a Korean Constitutional Court decision by its ID. Extracts case name, number, holdings, and reasoning for PIPA analysis.

Instructions

헌재 결정문 전문 (법제처 lawService · target=detc). 사건명·사건번호·결정요지·판시사항·전문 추출. PIPA 해석의 헌법적 근거(자기결정권 등) 추적. 긴 전문은 자동 축약. 다음: search_constitutional_decisions로 유사 사건, intelligent_law_search로 인용 조문 검색.

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": {
      "id": "<id>"
    },
    "name": "get_constitutional_decision_text"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	헌재결정례일련번호 (search_constitutional_decisions 결과의 [id=N])

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.1May 6, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description must fully disclose behavior. It mentions auto-summarization for long texts and the data source, but lacks details on auth requirements, rate limits, or safe read-only hint. Partial transparency.

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

Conciseness5/5

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

The description is concise, with key info front-loaded: purpose, extracted fields, auto-summarization, and follow-up suggestions. Every sentence adds value.

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?

For a simple retrieval tool with one parameter and no output schema, the description covers what it returns, the ID source, and auto-summarization. Could mention formatting details but sufficient for typical use.

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?

Only one parameter (id) with 100% schema coverage. The schema already explains the ID source. The description adds minor context (source, auto-summarization) but not essential beyond schema. Baseline 3 applies.

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 it extracts the full text of constitutional decisions, including case name, number, summary, etc. It also distinguishes from sibling search tools via '다음: search_constitutional_decisions로 유사 사건, intelligent_law_search로 인용 조문 검색.' The verb 'get' matches the tool name.

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 implies usage contexts (when full text is needed, auto-summarization for long texts) and suggests next steps. However, it does not explicitly state when not to use this tool versus other get_ tools for different document types.

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