dongguk-rule-mcp

get_rule_toc

Read-onlyIdempotent

Retrieve the table of contents (chapters, sections, articles) of a regulation from Dongguk University's integrated rule management system. Provide the law_id and optionally history_id for a specific version.

Instructions

규정 목차(장·절·조) 빠른 조회.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`law_id`	Yes
`history_id`	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.8/5.0

Behavior4/5

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

The annotations already declare read-only and idempotent behavior, and the description adds no conflicting or misleading information. It provides a hint that the operation is fast and focused, which is consistent with the annotation.

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 a single, concise sentence with no unnecessary words or repetition. It efficiently conveys the tool's core function.

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

Completeness3/5

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

While an output schema exists (so return values are presumably covered), the description omits any parameter context. The overall picture is mostly complete for the intended use, but the missing parameter details prevent full completeness.

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 has two parameters (law_id, history_id) but the description gives zero explanation of their meaning or usage. Since schema description coverage is 0%, the description fails to compensate, leaving the agent to infer from names alone.

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 retrieves the table of contents of a regulation, specifying the structure (chapters, sections, articles). It is distinct from sibling tools that handle content, search, history, or comparisons.

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?

The phrase 'quick lookup' implies the appropriate use case—retrieving the TOC rather than detailed content or deep search. While not explicitly comparing to alternatives, the tool's purpose is unambiguous enough to guide selection.

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

Deploy Server