klaws
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KLAWS_AUTH_TOKEN | No | Bearer token for HTTP authentication (used with --http) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_law_referenceA | Look up a bundled Korean law provision by ID and return its Korean and English names, a plain-language summary, the source URL on law.go.kr, a risk level, and (when available) the full Korean article text. Typically used to expand a related_laws ID returned by a scan. This is reference material, not legal advice. |
| list_detectorsA | List every available compliance risk detector with its id, name, description (the code pattern it looks for), and the related_laws it maps to. Use this to explain what klaws checks for, or to see which risks to expect before scanning. Takes no arguments. |
| scan_directoryA | Scan all matching files in a directory tree for possible Korean compliance risks across PIPA, the Network Act, the Credit Information Act, and the E-Commerce Act. Returns a JSON report where each finding has a detector_id, risk_level (HIGH or MEDIUM), file_path, line_number, snippet, a hedged message, and related_laws (provision IDs you can pass to get_law_reference). Findings are possible risks for review, not legal conclusions. Use this for a whole project or folder; use scan_file for a single file. |
| scan_fileA | Scan a single source file for possible Korean compliance risks and return the same JSON report shape as scan_directory. Use this to check one file (for example, the file currently being edited); use scan_directory to review a whole project. Findings are possible risks for review, not legal conclusions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: get_law_reference looks up laws by ID, list_detectors lists available detectors, scan_directory scans entire directories, and scan_file scans single files. There is no overlap or ambiguity.
All tool names follow a consistent verb_noun pattern in snake_case: get_law_reference, list_detectors, scan_directory, scan_file. The naming is predictable and uniform.
With 4 tools, the set is concise yet complete for its domain. It covers the necessary operations: listing detectors, scanning, and law reference lookup. No excess or deficiency.
The tool surface covers the full workflow: discover detectors (list_detectors), scan files (scan_directory/scan_file), and retrieve legal references (get_law_reference). There are no obvious gaps for the intended use case.