Skip to main content
Glama

텍스트 삽입

hwp_insert_text
Destructive

Insert text into HWP/HWPX documents at a specified section, paragraph, or character offset, using safe-write handling to preserve document integrity.

Instructions

지정한 섹션/문단/문자 오프셋 위치에 텍스트를 삽입합니다. 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>",
      "text": "<text>"
    },
    "name": "hwp_insert_text"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYes
forceNo
offsetNo
sectionNo
file_pathYes
paragraphNo
allow_lossNo
expected_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/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, but the description never says what is at risk of being lost or how insertion interacts with existing content. 'SafeWriter를 경유합니다' hints at an atomic/guarded write path yet is left unexplained, and nothing is said about the loss/force semantics implied by the parameters.

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 with the insertion target front-loaded and no filler. The brevity borders on under-specification rather than padding, so it is efficient but thin.

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

Completeness2/5

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

For a destructive, 8-parameter mutation tool with no output schema and no parameter documentation, the description leaves major gaps: loss/overwrite behavior, the role of expected_sha256 as a precondition, and what a successful result looks like. An agent could call it, but not confidently.

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 8 parameters, so the description must carry the burden. It only clarifies positional parameters (section/paragraph/offset) and that file_path should be absolute; the highest-risk parameters (force, allow_loss, expected_sha256) get no explanation at all.

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 (삽입/insert) and resource (텍스트), plus the granularity of the target location (섹션/문단/문자 오프셋). An agent can distinguish it from a replace or read tool, though no sibling is named explicitly.

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?

No statement of when to choose this over hwp_replace_text or hwp_fill_fields, and no preconditions such as whether the file must already exist or whether a lock is needed. Only an incidental path recommendation (절대 경로 권장) is offered.

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