Skip to main content
Glama

편집 계획 실행

hwp_run_plan
Destructive

Execute a declarative JSON edit plan to batch-modify HWP/HWPX documents with safe path binding, optional hash checks, and loss verification.

Instructions

rhwp 선언적 편집 계획서(plan JSON)를 일괄 실행합니다. input/output 경로는 SafeWriter가 안전하게 바인딩합니다. file_path는 절대 경로 권장.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "file_path": "<file_path>",
      "plan": "<plan>"
    },
    "name": "hwp_run_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
planYes
forceNo
file_pathYes
allow_lossNo
expected_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety bar is lower. The description adds genuinely useful context the annotations do not: SafeWriter binds input/output paths, and file_path should be absolute. It still says nothing about what a destructive run can destroy, how force/allow_loss change behavior, or how expected_sha256 gates execution.

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?

Three short sentences, front-loaded with what the tool does, then safety binding, then the path convention. No filler, but the brevity tips into under-specification for a destructive 5-parameter tool.

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?

For a destructive, nested-schema tool with no output schema, the definition is thin: the structure of the 'plan' object (additionalProperties=true, so unbounded) is never described, and the loss/force semantics that determine data risk are absent. A competent agent can identify the tool but not safely parameterize it.

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

Parameters2/5

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

Schema description coverage is 0% across 5 parameters, so the description carries the full burden and largely drops it. Only file_path gets any meaning (absolute path recommended); plan, force, allow_loss, and expected_sha256 remain entirely undefined, and two of them read like dangerous mutation flags.

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?

Names a specific verb and resource: batch-executing an 'rhwp declarative edit plan (plan JSON)'. That is concrete enough to distinguish it from single-edit siblings like hwp_insert_text or hwp_replace_text, though it never explicitly contrasts with hwp_rhwp_call, which plausibly takes lower-level calls.

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

Usage Guidelines2/5

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

The word '일괄' (batch) hints that this is the bulk route, but there is no explicit when-to-use vs when-not, no prerequisites, and no named alternative such as hwp_rhwp_call. An agent must infer the selection rule from the sibling list alone.

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