Loading ToolBench
HwpForge MCP server for AI-native HWPX document tools — read, edit, and generate Korean HWP/HWPX documents
HwpForge MCP server has 9 tools with basic descriptions but critical gaps in schema completeness and parameter documentation. Tool names follow verb_noun convention (inspect_document, read_document, edit_document), which is positive. However, input schemas visible in source show only top-level parameter names and types, no nested object schemas are defined for complex parameters like 'operations' (edit_document), 'stamp' (stamp_document), 'style' (apply_style), or 'options' (convert_md, to_md). Descriptions are present but generic (50-100 chars), lacking WHEN to use guidance, prerequisites, or actionable error recovery hints. No output schemas documented. No parameter constraints (enums, ranges, patterns) visible. Error handling not evident in source. Security concerns: edit_document and stamp_document accept file paths as strings with no apparent validation against path traversal. No evidence of permission gates or audit logging.
Apply style templates and formatting to HWPX documents
Convert Markdown content to HWPX document format
Compare two HWPX documents and identify differences
Edit HWPX document content, structure, and formatting
Exchange document format between HWPX and other formats
Inspect and analyze HWPX document structure, metadata, and content
Read and parse HWPX document content into structured format
Apply stamps, watermarks, or signatures to HWPX documents
Complex parameters (operations, stamp, style, options) lack nested schema definitions. 'operations' in edit_document is declared as array but no item schema provided, LLM cannot infer valid operation structure.
No output schemas documented. LLMs cannot plan downstream calls or extract required fields (e.g., does inspect_document return metadata? structure? content?).
File path parameters (path in inspect_document, read_document, edit_document, etc.) accept raw strings with no validation. No evidence of path traversal protection or sandboxing.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | F | 47 | 2026-07-28+ | v2 |
Export HWPX document to Markdown format
Descriptions are generic and under 100 chars. No guidance on WHEN to use each tool, prerequisites, or error recovery. E.g., 'Edit HWPX document content, structure, and formatting' does not explain what operations are valid or how to recover from failures.
No error handling guidance visible. Tools do not indicate which errors are retryable, user-fixable, or fatal. No recovery suggestions (e.g., 'If file not found, check path with inspect_document first').