Skip to main content
Glama
gmlcjf0326

claude-code-hwp-mcp

by gmlcjf0326

hwp_table_create_from_data

Create a new table from 2D array data with precise column/row widths in mm. First row can be styled as header with bold, centered text, and customizable background.

Instructions

2D 배열 데이터로 새 표를 생성합니다. col_widths/row_heights 로 mm 단위 정밀 레이아웃. (v0.7.3.1) cell 안 호출 시 자동으로 cell 폭 기반 col_widths 축소. row_heights 도 페이지 높이 자동 축소. treat_as_char 옵션으로 글자처럼 취급 on/off 제어 (cell 안 표는 한컴 자동 적용). (v0.7.6+) header_style=true 시 첫 행은 Bold + 가운데정렬 + 배경색 #E8E8E8 + 글자색 #333333 자동 적용 (header_bg_color/header_text_color 로 override).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYes2D 배열 데이터
alignmentNo본문 행 정렬 (기본 left). 헤더 행은 header_style=true 시 항상 가운데 강제.
col_widthsNo열 너비 (mm, 자동 축소 가능)
row_heightsNo행 높이 (mm, v0.7.3.1 자동 축소 추가)
header_styleNo첫 행 헤더 스타일 (v0.7.6+: Bold + 가운데정렬 + 밝은 회색 배경 #E8E8E8 자동 적용)
treat_as_charNov0.7.3.1 신규: 글자처럼 취급 on/off. cell 안 nested 표는 자동 true. top-level 표는 false 가 기본.
header_bg_colorNo헤더 배경색 [R,G,B] (기본 [232,232,232] 밝은 회색). header_style=true 일 때만 적용.
header_text_colorNo헤더 글자색 [R,G,B] (기본 [51,51,51] 진한 회색). header_style=true 일 때만 적용.
Behavior5/5

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

With no annotations, the description fully discloses behavioral traits: automatic column width reduction when called inside a cell, automatic row height adjustment, treat_as_char behavior for nested tables, and detailed header styling with defaults and overrides. This goes well beyond the schema.

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 lengthy but packs essential information with version markers and behavioral details. Each sentence adds value, though some redundancy could be trimmed for conciseness without losing clarity.

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

Completeness5/5

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

Given 8 parameters, full schema descriptions, and no output schema, the description provides extensive behavioral context including edge cases (inside cell, treat_as_char) and version info. It is sufficiently complete for an AI agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% with all parameters described, but the description adds significant context beyond schema: the auto-reduction behavior for col_widths/row_heights, treat_as_char default differences, and header style details including override parameters. This enriches understanding beyond the baseline of 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool creates a new table from 2D array data (specific verb+resource+input). It differentiates from sibling tools like hwp_table_add_row or hwp_table_delete_row by focusing on creation from data with precise layout options.

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 description implies usage for creating tables from arrays with layout options, but does not explicitly state when not to use it or mention alternatives among siblings. The context about automatic size adjustments within cells provides some guidance but no exclusions.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/gmlcjf0326/claude-code-hwp-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server