Skip to main content
Glama
EricSeokgon

egovframe-scaffold-mcp

by EricSeokgon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

CI 워크플로 생성

generate_egovframe_ci

Generate GitHub Actions CI workflows for eGovFrame projects, auto-detecting Maven/Gradle, setting JDK, and adding an optional supply-chain gate with SBOM and readiness assessment.

Instructions

프로젝트에 GitHub Actions CI 워크플로(빌드·테스트)를 생성합니다. 빌드도구(maven/gradle) 자동 감지, JDK 지정. supplyChain=true 면 이 서버의 CLI(npx egovframe-scaffold-mcp sbom·assess)로 SBOM 과 전환 준비도 평가서를 만들어 PR 요약에 등급을 남기고 failOn 기준(기본 supplyChain:D)을 넘으면 실패하는 공급망 게이트 job 을 추가합니다. dryRun으로 내용만 미리볼 수 있고, 실제 생성 시 기존 파일이 있으면 덮어쓰지 않고 거부합니다.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
jdkNoJDK 버전 (기본 17, 숫자·점만 허용)17
osvNo공급망 게이트에서 OSV 취약점 조회(--offline=false)
dryRunNotrue면 파일 생성 없이 내용만 반환
failOnNo공급망 게이트의 --fail-on 식supplyChain:D
projectDirYes프로젝트 디렉터리(절대경로 권장)
supplyChainNotrue 면 공급망 게이트 job 추가(v0.39): SBOM 생성 → 전환 준비도 평가서(등급을 PR 요약에) → 아티팩트, failOn 기준 초과 시 실패

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv0.40.0
    • addedInput schema / properties / failOn
      Added value: +{
+  "default": "supplyChain:D",
+  "description": "공급망 게이트의 --fail-on 식",
+  "pattern": "^(?:(?:migration|supplyChain):[ABCD]|[A-Za-z]+(?:>=?\\d+)?)(?:,(?:(?:migration|supplyChain):[ABCD]|[A-Za-z]+(?:>=?\\d+)?))*$",
+  "type": "string"
+}
    • addedInput schema / properties / osv
      Added value: +{
+  "default": true,
+  "description": "공급망 게이트에서 OSV 취약점 조회(--offline=false)",
+  "type": "boolean"
+}
    • addedInput schema / properties / supplyChain
      Added value: +{
+  "default": false,
+  "description": "true 면 공급망 게이트 job 추가(v0.39): SBOM 생성 → 전환 준비도 평가서(등급을 PR 요약에) → 아티팩트, failOn 기준 초과 시 실패",
+  "type": "boolean"
+}
  2. Changed2 schema fields changedv0.36.1
    • changedInput schema / properties / jdk / description
      Previous value: -"JDK 버전 (기본 17)"New value: +"JDK 버전 (기본 17, 숫자·점만 허용)"
    • addedInput schema / properties / jdk / pattern
      Added value: +"^[0-9]{1,2}(\\.[0-9]{1,3}){0,2}$"
  3. Addedv0.19.0

TDQS

A4.3/5.0
Behavior5/5

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

Annotations cover only the safety profile (readOnly=false, idempotent=false, destructive=false). The description goes well beyond them: it discloses the no-overwrite/refuse-on-existing-file behavior, the dryRun preview mode, the exact CLI invocation (npx egovframe-scaffold-mcp sbom·assess), the PR-summary grading, and the failOn default that can fail the job. This is unusually rich behavioral context for a mutation tool.

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?

Front-loads the core action in the first sentence, then layers conditional behaviors. Each sentence carries information, though the supply-chain sentence is dense and could be split for readability without losing content.

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?

For a 6-parameter mutation tool with no output schema, the description covers the destructive/refusal behavior, preview mode, and the optional gate job well. It could note what the generated workflow file path is or how the agent learns the result, but overall it is sufficient to call the 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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: supplyChain triggers an entire gate job with SBOM, readiness grading, and failure threshold, failOn defaults to supplyChain:D, dryRun returns content without writing, and the build tool is auto-detected rather than passed. These nuances help an agent reason about parameter interaction beyond the schema text.

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?

States a specific verb and resource — generates a GitHub Actions CI workflow (build/test) in the project — and adds distinguishing scope details (maven/gradle auto-detection, JDK, optional supply-chain gate job). An agent can tell this apart from sibling generators like generate_egovframe_sbom or generate_egovframe_report without opening the schema.

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?

Explains the conditions for the supplyChain and dryRun options, which is genuine conditional guidance, but never states when to choose this tool over sibling alternatives such as generate_egovframe_sbom or build_egovframe_project. Usage is implied rather than contrasted with alternatives.

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