egovframe-scaffold-mcp

프로젝트 진단

diagnose_egovframe_project

Read-onlyIdempotent

Scans existing eGovFrame projects and reports build system, RTE version, DbType, installed common components, and configuration problems in a read-only diagnosis.

Instructions

기존(스캐폴딩 도구로 만들지 않은 것 포함) 전자정부 표준프레임워크 프로젝트를 스캔해 빌드시스템·RTE 버전·DbType·설치된 공통컴포넌트(카탈로그 pathPrefixes 지문)·설정 문제를 진단합니다. 디스크를 변경하지 않는 읽기 전용입니다.

Input Schema

Name	Required	Description	Default
`projectDir`	Yes	진단할 프로젝트 디렉터리(절대경로 권장)

Output Schema

Name	Required	Description	Default
`issues`	Yes
`aiLayer`	Yes
`database`	Yes
`dbScripts`	Yes
`projectDir`	Yes
`buildSystem`	Yes
`egovVersion`	Yes
`hasManifest`	Yes
`suggestions`	Yes
`isEgovProject`	Yes
`detectedComponents`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.10.0Oct 31, 2026

addedOutput schema / properties / dbScripts

Added value: +{
+  "additionalProperties": {},
+  "properties": {
+    "componentScripts": {
+      "maximum": 9007199254740991,
+      "minimum": -9007199254740991,
+      "type": "integer"
+    },
+    "compose": {
+      "type": "boolean"
+    },
+    "prepared": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "componentScripts",
+    "prepared",
+    "compose"
+  ],
+  "type": "object"
+}

changedOutput schema / required

Previous value: -[
-  "projectDir",
-  "isEgovProject",
-  "buildSystem",
-  "egovVersion",
-  "database",
-  "detectedComponents",
-  "aiLayer",
-  "hasManifest",
-  "issues",
-  "suggestions"
-]New value: +[
+  "projectDir",
+  "isEgovProject",
+  "buildSystem",
+  "egovVersion",
+  "database",
+  "detectedComponents",
+  "aiLayer",
+  "hasManifest",
+  "issues",
+  "suggestions",
+  "dbScripts"
+]

Changed2 schema fields changedv1.6.0Oct 26, 2026
- removedInput schema / additionalProperties
```
Removed value: -false
```
- changedOutput schema / properties / detectedComponents / items / additionalProperties
```
Previous value: -trueNew value: +{}
```

Changed1 schema field changedv0.36.1Oct 4, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "aiLayer": {
+      "type": "boolean"
+    },
+    "buildSystem": {
+      "enum": [
+        "maven",
+        "gradle",
+        "unknown"
+      ],
+      "type": "string"
+    },
+    "database": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "detectedComponents": {
+      "items": {
+        "additionalProperties": true,
+        "properties": {
+          "id": {
+            "type": "string"
+          },
+          "matchedPrefix": {
+            "type": "string"
+          },
+          "name": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "id",
+          "name",
+          "matchedPrefix"
+        ],
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "egovVersion": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "hasManifest": {
+      "type": "boolean"
+    },
+    "isEgovProject": {
+      "type": "boolean"
+    },
+    "issues": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "projectDir": {
+      "type": "string"
+    },
+    "suggestions": {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    }
+  },
+  "required": [
+    "projectDir",
+    "isEgovProject",
+    "buildSystem",
+    "egovVersion",
+    "database",
+    "detectedComponents",
+    "aiLayer",
+    "hasManifest",
+    "issues",
+    "suggestions"
+  ],
+  "type": "object"
+}

Addedv0.19.0Jul 15, 2026

TDQS

A3.5/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is clear. The description adds that it supports existing non-scaffolded projects, but its read-only statement largely repeats annotations and it provides no additional permission, rate-limit, or side-effect context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences and front-loads the scan/diagnose action and scope. It is dense but has no redundant filler, apart from the read-only statement already covered by annotations.

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?

An output schema exists and the single parameter is fully documented in the schema, so the description only needs to explain purpose and scope. It does that well, including the non-scaffolded project case, though it could be stronger by explicitly routing agents away from similar validation or dependency-check tools.

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?

There is one parameter, projectDir, and schema description coverage is 100%, with the schema already recommending an absolute path. The description identifies the target as a project but does not add path syntax or format meaning beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: scanning and diagnosing an existing eGovFrame project. It enumerates concrete diagnostic areas (build system, RTE version, DbType, common components, configuration issues) and clarifies that non-scaffolded projects are included, though it does not explicitly distinguish this from validate_egovframe_project or check_egovframe_dependencies.

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

Usage Guidelines3/5

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

The description implies when to use it by specifying existing projects, including ones not created by scaffolding tools, but it gives no explicit when-not guidance and does not name alternatives such as validate_egovframe_project or check_egovframe_dependencies.

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

Deploy Server