Skip to main content
Glama
Sign In
EricSeokgon

egovframe-scaffold-mcp

by EricSeokgon
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

공통컴포넌트 제거

remove_egovframe_components
Destructive

Removes eGovFrame components from the install manifest, rejecting changed or dependent files; supports dry-run preview and force backups before deletion.

Instructions

add_egovframe_components로 조립한 컴포넌트를 제거합니다. 설치 매니페스트에 기록된 파일만 삭제하며, 다른 설치 컴포넌트가 의존하거나 설치 시점 hash와 달라진 파일은 기본 거부합니다. force=true는 remove-backup/에 사본을 만든 뒤 트랜잭션 제거하며, dryRun 미리보기를 지원합니다.

Input Schema

NameRequiredDescriptionDefault
forceNo사용자 수정·hash 미검증 파일도 remove-backup/에 백업한 뒤 제거
dryRunNotrue면 삭제 없이 대상만 미리보기
componentsYes제거할 컴포넌트 id 목록
projectDirYes대상 프로젝트 디렉터리

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.6.0
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Changed1 schema field changedv0.21.0
    • addedInput schema / properties / force
      Added value: +{
+  "default": false,
+  "description": "사용자 수정·hash 미검증 파일도 remove-backup/에 백업한 뒤 제거",
+  "type": "boolean"
+}
  3. Addedv0.19.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say destructiveHint=true; the description goes far beyond, disclosing that only manifest-recorded files are deleted, that dependency-shared and hash-mismatched files are refused by default, that force backs up to remove-backup/ before transactional removal, and that a dryRun preview exists. This is exactly the pre-mutation context an agent needs.

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?

Three compact sentences, front-loaded with what is removed, then the safety gate, then the escape hatch. No filler and no repetition of the schema.

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?

For a destructive, non-idempotent mutation with no output schema, the description covers scope, refusal conditions, backup location, transactionality, and preview mode. What happens to the project afterwards is inferable; nothing needed to call it safely is missing.

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; the description still adds value by explaining force as backup-then-transactional-remove and dryRun as a preview, and by introducing the install-time hash validation concept that the schema fields only hint at.

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 (add_egovframe_components로 조립한 컴포넌트), and explicitly names the inverse sibling in the first sentence. An agent can distinguish this from add/reassemble tools without inspecting schemas.

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?

Ties usage to the counterpart tool (add_egovframe_components) and spells out the default refusal conditions, which tells the agent when the call will be rejected. It does not, however, say when to prefer this over reassemble_egovframe_components or when force should be considered acceptable, leaving a sibling-selection gap.

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