Skip to main content
Glama

rhwp 도구 직접 호출

hwp_rhwp_call
Destructive

Calls any rhwp tool directly for HWP/HWPX editing, routing write outputs through temporary-file validation and atomic replacement.

Instructions

rhwp 가 제공하는 180여 개 전체 도구 중 하나를 직접 호출하는 탈출구입니다. 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>",
      "tool_name": "<tool_name>"
    },
    "name": "hwp_rhwp_call"
  }
}

Input Schema

NameRequiredDescriptionDefault
forceNo
is_writeNo
argumentsNo
file_pathYes
tool_nameYes
allow_lossNo
expected_sha256No

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

The description adds useful behavior beyond the annotations: write tools that accept an output argument are routed through SafeWriter for temporary output, validation, and atomic replacement, and absolute file_path is recommended. It does not explain what happens on validation failure, whether original files are preserved, how the destructiveHint risk manifests, or what force/allow_loss/is_write do. The annotations already declare destructive and non-read-only behavior, so the added SafeWriter context is helpful but incomplete.

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?

The description is short, front-loaded, and free of filler, with three sentences that each add some information. It is appropriately concise, though the terse structure does not compensate for the missing parameter and safety details.

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 complex, destructive generic dispatcher with seven parameters, a nested arguments object, and no output schema, the description is far too thin. It provides a high-level purpose and one safety mechanism but omits essential details about tool selection, argument forwarding, safety flags, failure behavior, and return values.

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%, so the description must carry parameter meaning, but it only clarifies file_path as an absolute path and loosely references write tools with an output argument. It leaves tool_name, the nested arguments object, force, is_write, allow_loss, and expected_sha256 completely unexplained, which is a major gap for a 7-parameter dispatcher.

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?

The description states a specific verb and resource: directly calling one of rhwp's 180+ tools as an escape hatch. It distinguishes this dispatcher from the named sibling wrappers by framing it as a generic fallback, though it does not explicitly compare itself to any sibling.

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?

The phrase 'escape hatch' implies this should be used when a dedicated wrapper is unavailable, which is useful implied guidance. However, there is no explicit when-to-use/when-not-to-use rule, no warning to prefer specific sibling tools, and no guidance on choosing among the 180 underlying tools.

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