dongguk-rule-mcp

search_rule_deep

Read-onlyIdempotent

Search the full text of multiple regulations to find relevant rules. Use this for cross-regulation queries; for a single regulation, use lookup_dongguk_rule instead.

Instructions

여러 규정의 전문을 탐색해야 할 때만 사용하는 보조 도구. 단일 규정 질문에는 lookup_dongguk_rule을 사용하세요.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`top`	No
`query`	Yes
`per_doc`	No

Output Schema

TableJSON Schema

Name	Required	Description
`ok`	Yes	도구 실행 성공 여부
`data`	No	성공 시 구조화 결과
`tool`	Yes	실행한 도구 이름
`error`	No	실패 시 구조화 오류

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.10.0Sep 9, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "성공 시 구조화 결과",
+      "type": "object"
+    },
+    "error": {
+      "description": "실패 시 구조화 오류",
+      "properties": {
+        "code": {
+          "type": "string"
+        },
+        "details": {
+          "type": "object"
+        },
+        "hint": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "code",
+        "message"
+      ],
+      "type": "object"
+    },
+    "ok": {
+      "description": "도구 실행 성공 여부",
+      "type": "boolean"
+    },
+    "tool": {
+      "description": "실행한 도구 이름",
+      "type": "string"
+    }
+  },
+  "required": [
+    "ok",
+    "tool"
+  ],
+  "type": "object"
+}

First observedv0.4.0Jul 4, 2026

TDQS

A3.9/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the behavioral traits. The description adds no extra behavioral context beyond these, so it meets the baseline but does not exceed it.

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 description is concise, using two short sentences to convey the purpose and usage conditions without any unnecessary information or repetition.

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

Completeness4/5

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

The description provides enough context to differentiate this tool from siblings like search_rule and lookup_dongguk_rule by highlighting the 'full text' and 'multiple regulations' aspects. It does not mention output format, but that is not required for basic usage guidance.

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

Parameters1/5

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

The schema provides no descriptions for the parameters (query, top, per_doc), and the description does not explain their meanings or expected formats. There is essentially no guidance on how to use these parameters, leaving the agent to guess.

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 description clearly states the tool's purpose: searching the full text of multiple regulations. It also distinguishes itself from lookup_dongguk_rule, which is for single regulation questions, making the intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage conditions: use only when searching full text of multiple regulations, and advises using lookup_dongguk_rule for single regulation questions. This gives clear when-to-use and when-not-to-use guidance.

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

Deploy Server