Skip to main content
Glama

페이지 이미지 렌더링

hwp_render_page

Render a specific HWP/HWPX page or all pages to PNG or SVG and return the saved image path for visual inspection.

Instructions

문서 페이지를 PNG 또는 SVG 이미지 파일로 렌더링하여 저장 경로를 반환합니다(시각 확인용). page는 0부터 시작하며, -1이면 전체 페이지를 렌더합니다. 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>"
    },
    "name": "hwp_render_page"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNo
formatNopng
file_pathYes
output_dirNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false and destructiveHint=false, and the description usefully confirms the tool writes a file and returns its path, which explains the non-read-only annotation. However it omits whether an existing file at the target path is overwritten, what the default output_dir is, and whether rendering many pages is costly.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with purpose then parameter semantics, with no filler. Every clause conveys information an agent needs before calling.

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

Completeness4/5

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

No output schema exists, and the description correctly states the return value (저장 경로). Combined with page/format/path semantics this is nearly sufficient; the remaining gap is output_dir behavior and default output location for a tool that produces files.

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?

With 0% schema description coverage the description must carry the load, and it does for three of four parameters: page indexing (0-based, -1 for all pages), format values (PNG or SVG), and file_path guidance (absolute path recommended). Only output_dir is left undefined.

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?

States a specific verb and resource (문서 페이지를 PNG 또는 SVG 이미지 파일로 렌더링) plus the returned artifact (저장 경로), and the parenthetical (시각 확인용) separates it from text-extraction siblings like hwp_get_text or hwp_table_view.

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 (시각 확인용) implies the intended use case — checking layout visually — but there is no explicit when-to-use/when-not-to-use guidance and no named alternative for text-only extraction. Usage is inferable rather than stated.

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