Skip to main content
Glama
Sign In

1gateway

by io.github.code0xff
OverviewDiscussionsAdmin

Korean statute text by name or article (Ministry of Government Legislation), unaltered with attribution

kr_law

Use when you need the official text of a South Korean statute, decree or rule, or one article of it. Statutes only: no court decisions or personal data. Input: q (statute name in Korean, e.g. 근로기준법) or mst (law serial no.), optional article (e.g. 2), limit (articles, 1-100, default 30). Output: JSON law metadata (ministry, effective date), articles [{label,title,text}] in original Korean, official URL, attribution. Example: ?q=근로기준법&article=2 Price: $0.0045 USDC (Base or Solana) via x402.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "kr_law"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoStatute name in Korean (exact name preferred), e.g. 근로기준법. Required unless mst is given.
mstNo법령일련번호 (law serial number) from a previous answer
limitNoMax articles when no article is given (default 30)
articleNoSingle article number, e.g. 2 or 제2조

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations provided, the description carries the disclosure burden and delivers: it describes the output shape (metadata, articles array, official URL, attribution), states content is original Korean, and reveals the payment mechanism ($0.0045 USDC via x402). Rate limits and error behavior are not mentioned, keeping it from a 5.

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?

Front-loaded and labeled (Input/Output/Example), with zero wasted words. Each segment—scope, exclusions, parameters, output, example, price—earns its place for an agent deciding whether to call.

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

Completeness5/5

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

There is no output schema, and the description fully explains the return values (metadata, articles, URL, attribution) so an agent knows what to expect. Combined with scope exclusions and payment info, nothing essential is missing.

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 description coverage is already 100%, so the baseline is 3. The description adds useful detail beyond the schema—the limit range (1-100) and concrete examples for q (근로기준법) and article (2)—which slightly edges toward but does not clearly exceed the schema baseline.

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?

States a specific verb and resource ('official text of a South Korean statute, decree or rule, or one article of it') and scopes it precisely. It is easily distinguished from sibling kr_* tools (company, address, weather, trade) which cover entirely different domains.

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?

Opens with an explicit 'Use when...' context and adds a clear when-not boundary ('Statutes only: no court decisions or personal data'). It does not name a specific alternative sibling to route to, so it falls short of full 5-level routing guidance.

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

All 1gateway toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources