Skip to main content
Glama

get_external_links

Need external links to Korean legal documents? Get URLs for laws, precedents, interpretations, ordinances, and admin rules by providing the link type and identifier.

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?

No annotations provided. Description lacks any behavioral traits such as read-only nature, side effects, or required permissions. Agent cannot infer what happens when the tool is called.

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?

While very short, the single sentence is not informative and fails to earn its place. It provides no meaningful guidance.

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 severely incomplete. Agent lacks understanding of return format, parameter combinations, or when to use specific params.

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 descriptions are provided for all parameters (100% coverage), so baseline is 3. The tool description adds no extra meaning beyond the schema.

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

Purpose2/5

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

Description '법령 외부 참조 링크' (Legal external reference link) is vague and essentially restates the tool name 'get_external_links'. It does not specify whether the tool retrieves, generates, or lists links, nor does it differentiate from the sibling '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 versus alternatives like 'get_alio_external_links' or other search tools. No context on prerequisites or scenarios.

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

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