Skip to main content
Glama

누름틀 필드 채우기

hwp_fill_fields
Destructive

Fill named fields in HWP/HWPX documents with supplied values, using checked writes to update form content and 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>",
      "data": "<data>"
    },
    "name": "hwp_fill_fields"
  }
}

Input Schema

NameRequiredDescriptionDefault
dataYes
forceNo
passwordNo
file_pathYes
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 profile is partly covered. The description adds only 'goes through SafeWriter' (unexplained — backup? atomic write?) and an absolute-path recommendation; it does not say what gets overwritten, whether existing field values are lost, or how force/allow_loss govern data loss, which matters for a destructive mutation.

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 the action and resource, with no wasted wording. Brevity is appropriate, though it comes at the cost of the missing details noted above.

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 write tool with six parameters, two loss-control flags, a password, an integrity hash, and no output schema, the description is far too thin. An agent cannot tell what SafeWriter guarantees, when allow_loss is required, or what a successful fill returns.

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 six parameters, so the description must compensate and does not. It explains only file_path (absolute path recommended) and implies data maps names to values, while force, allow_loss, password, and expected_sha256 — including the nested data object's string-value constraint — are left entirely undefined.

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?

States a specific verb and resource: fills named click-here (누름틀) fields in a document, and indicates values are matched by field name. This is clearer than the title alone, though it does not distinguish itself from the sibling hwp_fill_cells (table cells) or hwp_replace_text.

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 guidance on when to use this versus hwp_fill_cells, hwp_replace_text, or hwp_insert_text. It also never states the prerequisite that the document must already contain 누름틀 fields, so an agent has no basis for choosing among the fill/replace siblings.

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