Skip to main content
Glama
Sign In
Korean Law MCP Server

Korean Law MCP Server

by yunhyok
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

korean_law_setup

Read-onlyIdempotent

Checks local configuration without network access and keeps the OC value hidden, so you can diagnose setup issues safely.

Instructions

Check local configuration without network access or revealing the OC value.

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": "korean_law_setup"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.1

TDQS

A4.7/5.0
Behavior5/5

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

While annotations cover safety (read-only, non-destructive), the description adds vital operational constraints. Explicitly stating it works 'without network access' and 'without revealing the OC value' provides unique, actionable behavioral context.

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?

The definition is a single, highly optimized sentence. It packs multiple constraints (local, offline, secrecy) into an extremely concise package without being verbose.

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?

Given the 0-parameter setup, the presence of robust annotations, and the existence of an output schema, the description provides all necessary high-level constraints an agent needs to select this tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Since the tool has zero parameters, the schema coverage is 100%. The description correctly validates the parameter-less nature of the tool, achieving the baseline score for 0 input parameters.

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?

The purpose is crystal clear: checking local configuration. It successfully distinguishes itself from the sibling tools (search/get documents) by specifying the focus on local system setup.

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?

It provides excellent context for use by highlighting the constraint of operating without network access. This implicitly defines when it should be used over any network-dependent tool.

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