Skip to main content
Glama
scvcoder

korean-law-alio-mcp

by scvcoder

get_external_links

Generate external reference links for Korean laws, precedents, interpretations, ordinances, and administrative rules. Provide link type and relevant IDs to obtain direct URLs to authoritative legal sources.

Instructions

[링크] 법령 외부 참조 링크.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
linkTypeYes링크 유형: law (법령), precedent (판례), interpretation (해석례), ordinance (자치법규), admin_rule (행정규칙)
lawIdNo법령ID (법령 링크 생성 시)
mstNo법령일련번호 (법령/자치법규 링크 생성 시)
lawNameNo법령명 (한글 URL 생성용, 예: '관세법')
joNo조문 번호 (한글 URL 생성용, 예: '제38조')
precedentIdNo판례일련번호 (판례 링크 생성 시)
interpretationIdNo법령해석례일련번호 (해석례 링크 생성 시)
adminRuleIdNo행정규칙일련번호 (행정규칙 링크 생성 시)
ordinanceIdNo자치법규ID (자치법규 링크 생성 시)
Behavior1/5

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

With no annotations, the description bears full responsibility but fails to disclose any behavioral traits (e.g., parameter dependencies, error handling, or output format). Only a vague one-line description.

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

Conciseness2/5

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

Extremely concise but under-specified; the single sentence does not justify its brevity as it omits critical information about tool behavior and usage.

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

Completeness1/5

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

Given 9 parameters, no output schema, and no annotations, the description is grossly inadequate. It does not explain how parameters interact, return values, or provide sufficient context for proper invocation.

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?

Input schema has 100% coverage with parameter descriptions, so baseline is 3. The description adds no additional meaning beyond the schema.

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 'Statutory external reference links' indicates a get operation on external links, but it lacks specificity about the resource and does not differentiate from sibling tools like get_alio_external_links.

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 vs alternatives such as get_alio_external_links or search_law. No exclusions or context provided.

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/scvcoder/korean-law-alio-mcp'

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