Skip to main content
Glama
Sign In
korean-law-alio-mcp

korean-law-alio-mcp

by scvcoder
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

get_interpretation_text

Retrieve the full text of a legal interpretation from Korean law using its serial number, enabling detailed review and citation.

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

Input Schema

NameRequiredDescriptionDefault
idYesLegal interpretation serial number (법령해석례일련번호) from search results
caseNameNoCase name (optional, for verification)
apiKeyNo법제처 Open API 인증키(OC). 사용자가 제공한 경우 전달

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.5/5.0
Behavior2/5

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

No annotations are present, so the description bears full responsibility for behavioral disclosure. It does not mention read-only nature, authentication needs, rate limits, or any side effects.

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 extremely short—a single phrase. While concise, it lacks substantive information, making it minimally adequate.

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 the absence of an output schema and the presence of many similar sibling tools, the description provides insufficient context. It does not describe return value format, pagination, or prerequisites.

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 all three parameters. The description adds no extra meaning beyond what the schema already provides, meeting the baseline.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it retrieves the full text of an interpretation case. It clearly identifies the verb (조회=search/retrieve) and resource (해석례=interpretation case), but it essentially paraphrases the tool name without adding detail to distinguish it from many similar 'get_*_text' sibling tools.

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 is provided on when to use this tool versus alternatives like search_interpretations or other get_text tools. The description lacks context for proper selection.

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

Deploy Server

Other Tools