An MCP server for creating, editing, and manipulating HWP (Hangul Word Processor) documents through a Go interface
This MCP server has 27 tools with reasonable naming and descriptions, but significant structural gaps. All tools are explicitly registered in main.go with mcp.NewTool() and handler functions, so schemas are visible. However, most tools lack proper input validation schemas, parameters are declared but many lack type constraints, enums, or validation rules. Tool descriptions are present but often generic (10-50 chars), which is below the 50-200 char baseline for LLM-optimized docs. No output schemas are documented, forcing LLMs to guess what each tool returns. Error handling is invisible in the provided code, no recovery guidance, no error classification, no actionable failure messages. Parameter relationships are undocumented (e.g., hwp_insert_image has mutually exclusive sizing modes but does not explain the interaction). The server is domain-specific (HWP document manipulation) with high WRITE risk across most tools, but lacks confirmation or dry-run patterns for destructive operations. Tool composition is reasonable, most tools do one thing, but some combine concerns (e.g., hwp_create_document_from_text handles text + title + font in one call, forcing bundle reasoning). Security: no visible audit logging, no permission gates, no input sanitization hints.
Execute multiple HWP operations in sequence
Close the HWP document and connection
Create a new HWP document
Create a complete document from specification (report, letter, memo)
Create a new document from text content
Create a table and fill it with data
Fill table column with sequential numbers
Fill existing table with data
Output schemas undocumented. No tool documents what fields it returns, forcing LLMs to infer structure from tool names and hope. This blocks tool chaining and increases hallucination risk.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-22 | D | 51 | 2026-07-28+ | v2 |
| 2026-03-09 | F | 25 | - | v1 |
Get the text content of the current document
Insert an image at the current cursor position with full Python functionality
Insert a column to the left of the current position
Insert a row below the current position
Insert a new paragraph
Insert a column to the right of the current position
Insert a table at the current cursor position
Insert text at the current cursor position
Insert a row above the current position
Merge selected table cells
Merge adjacent tables into one table
Move cursor to the left cell
Move cursor to the lower cell
Move cursor to the right cell
Move cursor to the upper cell
Open an existing HWP document
Ping pong test function
Save the current HWP document
Set font properties with color support
Descriptions too generic or minimal. 16 tools (hwp_create, hwp_close, hwp_ping_pong, hwp_insert_paragraph, hwp_insert_left_column, hwp_insert_right_column, hwp_insert_upper_row, hwp_insert_lower_row, hwp_move_to_left_cell, hwp_move_to_right_cell, hwp_move_to_upper_cell, hwp_move_to_lower_cell, hwp_merge_table_cells, hwp_merge_tables, and others) have descriptions under 50 characters. These lack context for LLM tool selection. Baseline for A+ tools is 50-200 chars.
No error handling guidance. The source code shows tool registration but no visible error recovery hints, error classification (retryable vs fatal), or actionable error messages. LLMs cannot know whether to retry, ask user, or abort.
hwp_insert_image has 11 parameters with complex mutual exclusivity (use_original_size, max_width/max_height vs width/height; keep_aspect_ratio mode). Parameter relationships are undocumented, LLMs cannot infer which combinations are valid.
Destructive operations lack confirmation or dry-run support. 21+ tools perform WRITE operations (create, delete, merge, fill) with no mention of confirmation, preview, or undo capability. Agents can accidentally corrupt documents.
hwp_set_font color parameter accepts free-form strings but description lists only 7 examples (black, red, blue, green, yellow, purple, cyan). No enum constraint. LLMs may hallucinate unsupported colors like 'orange' or 'magenta'.
hwp_batch_operations and hwp_create_complete_document accept JSON strings as input ('operations' and 'spec' parameters). No schema validation or format documentation. LLMs will hallucinate JSON structures; any parse error crashes silently.
No parameter descriptions for numeric ranges. hwp_insert_table accepts 'rows' and 'cols' with no min/max (e.g., 1 - 1000?). hwp_fill_column_numbers 'start' and 'end' have no range guidance. LLMs may pass absurd values.
hwp_fill_table_with_data and hwp_fill_column_numbers expect 1-based indexing but do not state this. LLMs accustomed to 0-based APIs will likely pass wrong offsets.
No audit logging or permission gates visible. Tools modify documents with no indication of user context, audit trail, or permission checks. Compliance and debugging become impossible.